[Webkit-unassigned] [Bug 115396] New: Constructing the KURL from base + fragment ref is problematic for data: URI

[bugzilla-daemon at webkit.org]

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

           Summary: Constructing the KURL from base + fragment ref is
                    problematic for data: URI
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: SVG
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: rniwa at webkit.org
                CC: ap at webkit.org, beidson at apple.com, zimmermann at kde.org


We should consider merging https://chromium.googlesource.com/chromium/blink/+/2274b648033402fc691536b45daf8b00486dc72a

Constructing the KURL from base + fragment ref is problematic for data: URI, as it is not a
hierarchical scheme and relative resolution fails.

Luckily, this is avoidable: the only reason for constructing a KURL is to compare against the
document URL, but the comparison ignores the fragment anyway (equalIgnoringFragmentIdentifier).
This is equivalent to a base-only comparison, which is the approach proposed in this patch.

No test: the issue only triggers when the document url is data: URI based, and DRT doesn't seem to
support opening such a scheme directly. Current baseURI vs. document URL validation is covered by
existing tests.

(For background on why we perform such validation in the first place, see
https://bugs.webkit.org/show_bug.cgi?id=63283
https://bugzilla.mozilla.org/show_bug.cgi?id=308590)

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