RESOLVED WONTFIX Bug 91237
[Chromium] External <use> xlink:href references do not work
https://bugs.webkit.org/show_bug.cgi?id=91237
Summary [Chromium] External <use> xlink:href references do not work
Dirk Schulze
Reported 2012-07-13 07:07:42 PDT
External <use> xlink:href references do not work on Chromium. See patch and tests for WebKit on bug 12499.
Attachments
jay
Comment 1 2013-04-09 00:44:27 PDT
Stephen, Please can you comment and supply a rationale explaining why this bug is marked wontfix? As you will know, external <use> is part of the SVG specification: the ‘use’ element can reference any local or non-local resource http://www.w3.org/TR/SVG/linking.html#processingIRI and has been implemented by all the other major browsers. External <use> offers accessibility, efficiency and maintenance advantages, for example: Developing countries have limited narrow band internet connections, and the benefits of downloading once only are significant.[1] People with learning disabilities or low literacy also benefit from, or may rely on similar graphics, and may be disadvantaged by this decision. Jonathan Chetwynd http://www.pcyberia.com [1] 16 UK weather icons in 2kb here: http://upload.wikimedia.org/wikipedia/commons/5/50/Weather-icons.svg
Stephen Chenney
Comment 2 2013-04-09 05:26:12 PDT
(In reply to comment #1) > Stephen, > > Please can you comment and supply a rationale explaining why this bug is marked wontfix? There is no longer Chromium development in WebKit. Move all discussion to: https://code.google.com/p/chromium/issues/detail?id=229081
jay
Comment 3 2013-04-09 07:41:45 PDT
fixed has a particular meaning, as I would expect you are aware. the explanation given does not qualify, and is extremely confusing for new visitors. please advise further.
Stephen Chenney
Comment 4 2013-04-09 07:53:17 PDT
I'm not sure what you would like to happen (apart from getting the bug fixed). This is the WebKit bug tracker, and Chromium is no longer using WebKit, so the bug will not be fixed in WebKit. Hence, WontFix. The bug now exists in Chromium's bug tracker, where it is currently untriaged but tagged for the SVG team to look at. All you need to do is start using that forum for discussion.
Note You need to log in before you can comment on or make changes to this bug.