[Webkit-unassigned] [Bug 44047] New: Stylesheets that use local references are treated as local to the SVG document

[bugzilla-daemon at webkit.org]

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

           Summary: Stylesheets that use local references are treated as
                    local to the SVG document
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: SVG
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: dholbert at mozilla.com
                CC: zimmermann at kde.org


Created an attachment (id=64476)
 --> (https://bugs.webkit.org/attachment.cgi?id=64476)
testcase 1

STEPS TO REPRODUCE:  Load attached testcase.
EXPECTED RESULTS:    The teal line should have no arrowhead.
ACTUAL RESULTS:      In WebKit, the teal line has an arrowhead.

NOTE: My example uses a data URI for the stylesheet, for simplicity of bug-attaching.  However, this happens for "real" (non-data-URI) external stylesheets as well.

EXPLANATION: In the testcase, the reference "url(#myMarker)" ends up looking for that node in our our SVG document. This is incorrect -- per specification, that identifier should use the URI of the stylesheet instead.  See in particular:
http://www.w3.org/TR/CSS21/syndata.html#uri
"
In order to create modular style sheets that are not dependent on the absolute
location of a resource, authors may use relative URIs. Relative URIs (as defined
in [RFC3986]) are resolved to full URIs using a base URI. RFC 3986, section 5,
defines the normative algorithm for this process. For CSS style sheets, the base
URI is that of the style sheet, not that of the source document.
"

Filing this based on the following (invalid) Mozilla bugs:
(they were filed for Mozilla *not* placing the arrowhead, but that's in fact the correct behavior)
  https://bugzilla.mozilla.org/show_bug.cgi?id=587490
  https://bugzilla.mozilla.org/show_bug.cgi?id=309612
See those bugs for more discussion of this issue.

Recent Firefox & Opera both give EXPECTED RESULTS.  Webkit* gives ACTUAL RESULTS.

* I tested these WebKit-based browsers on Ubuntu 10.04:
    Chromium 6.0.495.0 (56150)
    Midori 0.2.2 (WebKitGTK+ 1.1.21)

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