Follow-up for https://bugs.webkit.org/show_bug.cgi?id=63283
Keeping this as a reminder for this bug: > > Source/WebCore/css/SVGCSSStyleSelector.cpp:396 > > - svgstyle->setMarkerEndResource(SVGURIReference::getTarget(s)); > > + svgstyle->setMarkerEndResource(SVGURIReference::fragmentIdentifierFromIRIString(s, m_element->document())); > > Oops, we silently assume same-document references here! If we just extract the fragment identifier here, we're going to ignore any external URL. > We should store the whole IRI string here, and lookup the targetelmenetForIRIString later in rendering/ when we actually use the marker end resource. > > That affects all usages of fragmentIdentifierFromIRIString - thery're all assuming same-doc refs, which is wrong. > (Parts from our IRC discussion) Cheers, Rob.
Hi Rob, any progress on this issue ? Blocked #12499 is realy annoying for larger SVG applications. Zbynek
Is anybody working on this bug? I'm interested in this topic and I'd like to work on it if there are no objections.
Just want to follow this bug.
Is there any progress on this? It’s practically crippling any non-trivial use case for SVG.
*** Bug 90955 has been marked as a duplicate of this bug. ***
I believe this bug refers to external SVG references with fragment URIs? External url references should work fine, with the caveat that fragment URIs do not work due to this longstanding issue: https://bugs.webkit.org/show_bug.cgi?id=6007 If this is indeed about the fragment URI bug, we should mark it as a duplicate of https://bugs.webkit.org/show_bug.cgi?id=91791. @Lea, to my knowledge nobody is working on this at the moment :(