[Webkit-unassigned] [Bug 110021] New: SVG use fragment identifier with display:none

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sat Feb 16 09:44:35 PST 2013


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

           Summary: SVG use fragment identifier with display:none
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Macintosh Intel
        OS/Version: Mac OS X 10.8
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: SVG
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: soccerjonp at hotmail.com
                CC: zimmermann at kde.org


Created an attachment (id=188715)
 --> (https://bugs.webkit.org/attachment.cgi?id=188715&action=review)
Example of this bug. A red circle should appear after 2 seconds.

This is probably easiest to describe with a minimal working example which I've attached. If using Chrome to view the example, you'll probably have to run it in a web server because Chrome restricts cross domain requests when referencing the local file. The correct behavior for this example is to see a red circle appear 2 seconds after loading the page. This example works in Firefox 17 and Opera 12.12.

In the example, we have an SVG inside a div element. The SVG consists entirely of a <use> element referencing an external SVG via a fragment identifier (xlink:href="test.svg#one"). The surrounding div has display:none set from the output, which is changed via javascript to display:block after 2 seconds. At this point the SVG should be visible, but it is not. This does work if instead of referencing an external SVG file, we reference one in the HTML document.

One reason it would be useful for this to be fixed is that it would allow you to have SVG sprites. You could define many fragments in an external SVG file and reference them individually in the HTML. This could reduce the number of HTTP requests.

-- 
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