[Webkit-unassigned] [Bug 68089] WebKit doesn't parse "#" as delimiter for fragment identifier in data URIs

[bugzilla-daemon at webkit.org]

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





--- Comment #18 from Adam Barth <abarth at webkit.org>  2011-09-20 10:39:54 PST ---
> The problem I want to solve here is interop. If you think Webkit's behavior is fine, please document it and propose it to the list.

I'm sorry that I don't have time to do that at the moment.  Previously I was working a full specification of URL handling, but I've stopped working on that spec.  You can find my work-in-progress here:

https://github.com/abarth/url-spec/blob/master/drafts/url.xml

> When you do that it would be good if you can describe how relative URIs should work in data: URIs.

It's pretty simple:

1) If the relative URL is an absolute URL, then the resolved URL is that absolute URL (appropriately canonicalized).

2) Otherwise, the resolved URL is an invalid URL.

Separately, trying to navigate to an invalid URL results in a navigation to about:blank.

In the spec, this is marked as a TODO:

        <t>TODO: If base-url's scheme is not hierarchical, we can't resolve as
        a relative URL.  We'll probably want to return an invalid URL.  Check
        what happens when resolving an empty string as a relative URL with a
        non-hierarchical base.</t>

>From the point of view of the spec, data URLs are not hierarchical, which essentially means we parse out the scheme and leave the remainder of the URL to be parsed by a scheme-specific parser.

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