[Webkit-unassigned] [Bug 15443] SVGImage does not support sub-resource loading

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jan 27 12:13:32 PST 2011


https://bugs.webkit.org/show_bug.cgi?id=15443





--- Comment #13 from Cosmin Truta <ctruta at chromium.org>  2011-01-27 12:13:31 PST ---
(In reply to comment #11)
> I did not take a look to the code of RenderSVGModelObject. But, if it checks the subresources, we should see two circles, since self-cycle.svg is the source, the first <image> loads the first subresource and should be drawn. IMHO it's important that we don't draw the circle a third time. Can you check this please?

Maybe I'm reading the spec the wrong way, but in Section 17.1.4 "Processing of IRI references", there's the following statement:
"IRI references that directly or indirectly reference themselves are treated as invalid circular references."

So we should only see the first circle. Everything that follows is derived from an invalid circular reference and should not be rendered.

There is no circle drawn a 3rd time, but that's because no sub-resource (be it circularly-referenced or not) is loaded after the first level. That's what I meant in point (1) in my comment #9. For example:
  main.svg contains <image xlink:href="subres1.svg"/>
  subres1.svg contains <image xlink:href="subres2.svg"/>
  subres2.svg contains <image xlink:href="subres3.svg"/> etc.

Only the elements in main.svg and subres1.svg are rendered, regardless of cycles, and that's because of the way in which subresources are loaded through SVGImage::dataChanged.
See Morley's comment #5 and his attachment 59767.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list