Re: what is the W3C SVG way to use an external css to style markers

Dr. Olaf Hoffmann :
> Ghislain Fabre:
>> Do you know if there is a W3C way to have
>> <the file that called  me>#markerintern5
>> that works for Opera and Firefox (and maybe for Chrome
>> and Safari) ?
> The method is to write '#markerintern5' if you mean it.
> If you know the name/URI of the file, for example
> '/my.svg' or 'http://example.org/my.svg', you may write
> as well '/my.svg#markerintern5' respectively
> 'http://example.org/my.svg#markerintern5'.
>
> Note, that there can be 'privacy/security considerations',
> if there are different domains in the game, here for
> example for the URI variant, it might be, that everything
> should be in one domain.
Thanks a lot Olaf for your reply.
I'm testing about two ways.
I have made an visual representation of the two ways in order to make it 
more easy to understand :
http://developpements.open-elearning.com/tests-divers/svg-and-marker02/visual-presentation-of-problem-markers-externalized.svg
http://developpements.open-elearning.com/tests-divers/svg-and-marker03/visual-presentation-of-problem-markers-internalized.svg

I have done today more test about the first way : with the markers 
externalized.

Thanks to your help, i have tested the method that you give me, and made 
other tests.

Here is the result of 9 different methods using url to try to access to 
markers that are externalized : 
http://developpements.open-elearning.com/tests-divers/svg-and-marker02/b.svg 
(and the files can be downloaded here : 
http://developpements.open-elearning.com/tests-divers/svg-and-marker02/test2.zip)

As Robert told me, everything failed for Chromium 37 and Safari 5.
Method 2, 4, 6, 8 and 9 works fine for Firefox 32 and Opera 12.6.

Method 2 is the same that method 6, the only difference is using ' or no.
Method 4 is the same that method 8, the only difference is using ' or no.

As you told me, so the w3c recommend using ', no ? (or the 
recommendation is that we can use both, with and without ?)

Method 6 is the same that method 8, the only difference is using ./ at 
the start or no.

Someone know if there is a recommendation from w3c to use or not use ./ 
at the start ? (marker-end:url('./markers.svg#marker1'); )

I will try the next time to make these tests but with the markers 
internalized.

>
> If the current version or 'nightly build' of a viewer
> has a problem with this (I did not check it here),
> one can report a bug  to the developers,
> if it is not already known.
> If a bug is already known or newly reported, there
> is sometimes a chance, that such a bug is fixed
> in future versions of the viewer, but one cannot rely
> on this assumption ;o) In several cases and viewers
> bugs are never fixed and as an author one can
> implicate, that such a viewer can be considered
> to have a permanently broken implementation.
> In the worst case you may find the broken behaviour
> being specified/documented in the next version of the
> format - and you can be relatively sure, that the feature
> is finally broken.
> Either one informs users about such broken features,
> if one needs to use such a feature or one does not use
> the feature, recommended by W3C or not.
> Often authors (like me) seem to overestimate
> that they need to publish specific intends,
> often it is more recreative to be only surprised
> or amused about bugs in viewers as to insist
> to publish something specific, that requires a
> broken feature ;o)
:) ok thanks a lot for these information and your attention. When i will 
finished all the tests, I will try to see if these bugs are already 
known for Chrome and Safari.

Best regards,

Ghislain

Received on Monday, 29 September 2014 23:10:33 UTC