- From: Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de>
- Date: Mon, 29 Sep 2014 17:16:19 +0200
- To: ghislain.fabre@open-elearning.com, www-svg@w3.org
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. 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) Olaf
Received on Monday, 29 September 2014 15:16:50 UTC