Issue metadata
Sign in to add a comment
|
SVG <use> in doesn't work
Reported by
vitaly.o...@gmail.com,
Mar 16 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11) AppleWebKit/601.1.56 (KHTML, like Gecko) Version/9.0 Safari/601.1.56 Example URL: Steps to reproduce the problem: http://css.yoksel.ru/assets/demo/svg-in-firefox/svg-has-base.html What is the expected behavior? What went wrong? The <use> element has 0 × 0 px size and icons are not displayed. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? Yes 48 version Does this work in other browsers? Yes Chrome version: <Copy from: 'about:version'> Channel: n/a OS Version: OS X 10.11 Flash Version: Sometimes it works on 50 version
,
Mar 16 2016
,
Mar 16 2016
This looks like issue 470608 - I don't really see how adding <base> would not have any effect. What happens here is that the xlink:href on the <use> resolves against the base URL of the document (as specified by <base> after it has been inserted.) So the possible "bug" is if cloneNode(true) is expected to not re-resolve any URLs in attributes - but AFAIK that's not specified.
,
Mar 16 2016
,
Mar 16 2016
Lets see if a bisect shows anything interesting.
,
Mar 16 2016
bisect for me yields a range of: https://www.google.com/url?q=https://chromium.googlesource.com/chromium/src/%2Blog/38b2f1369ee256717e05cc2f9c8ccbb449e6bdf2..6967287223ccbe29db1454e6ace0d412524aac25&sa=D&usg=AFQjCNGMbHnF0dN4JQpkQM4UOpwNcQYwzA Most notably containing: https://chromium.googlesource.com/chromium/src/+/d97f56157c1d119d3a0dda5d5d341e099f7f2b26 "SVG should consider base URI when resolving fragment URIs"
,
Mar 16 2016
Thanks blois. This was also reported by a google team in (internal bug link) go/b595322. @Schenney, do you have time to take a look at this?
,
Mar 17 2016
Also note that this also occurs if there's not an explicit <base> tag, but if the document is loaded via setting iframe.srcdoc.
,
Mar 17 2016
For 'srcdoc', the base URL is the base URL of the iframe element's node document (or "the document base URL of the Document's browsing context's browsing context container's node document" per spec lingo...) So it's the same issue. https://html.spec.whatwg.org/#document-base-url
,
Mar 21 2016
,
Apr 1 2016
,
Jun 4 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by vitaly.o...@gmail.com
, Mar 16 2016