[Webkit-unassigned] [Bug 147568] New: The SVG <image> element can only be loaded if it is a data uri or its SVGDocument is interactive

[bugzilla-daemon at webkit.org]

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

            Bug ID: 147568
           Summary: The SVG <image> element can only be loaded if it is a
                    data uri or its SVGDocument is interactive
    Classification: Unclassified
           Product: WebKit
           Version: 528+ (Nightly build)
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: SVG
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: sabouhallawa at apple.com
                CC: zimmermann at kde.org

The specs does not say a non-interactive SVG can't load sub-resources form the same origin. This has been limiting building a structure of SVG images. It has been also confusing because we allow loading the same image for interactive SVG document but we do not for non-interactive SVG document. The only reliable solution is to make the SVG self-contained by including the external resources as data uri images. This solution is also cumbersome since it enforces duplicating the same image data if it is referenced by multiple images. It also makes updating the data uri images a lengthy process especially for cases like including the company logo in all the SVG images.

Since there is nothing in the specs which prevents loading sub resources from an SVG image (at least from the same origin) and since it seems important feature in organizing the graphics documents and make sharing resources useful and effective, I proposing this change. I am collecting a list if issues I have found from testing my change and from discussing this change with other WebKit developers.

1. IE is the only browser which supports loading an image from an SVG. Chrome and FireFox does not allow SVG from loading external images except for interactive SVG images.
2. We need to handle the circular referencing the same way we do for <iframe>.
3. WebInspector might need to show the hierarchy of SVG image referencing.
4. The specs does not say if a data uri image can or can't reference external resource, but I think they should not. The data uri resources should be self contained. One implementation obstacle which makes it hard is the data uri resource does not have a URL so it is difficult to relate an external URL inside the data uri to the document which includes the data uri image itself.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150803/295dfeee/attachment.html>