This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20915 - data URL parsing
Summary: data URL parsing
Status: RESOLVED WORKSFORME
Alias: None
Product: WHATWG
Classification: Unclassified
Component: URL (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+urlspec
URL: http://url.spec.whatwg.org/#scheme-da...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-08 21:24 UTC by Ian 'Hixie' Hickson
Modified: 2013-08-19 16:22 UTC (History)
2 users (show)

See Also:

Attachments

Description Ian 'Hixie' Hickson 2013-02-08 21:24:02 UTC 
Nothing seems to make "data://" a parse error.
Comment 1 Anne 2013-02-12 09:43:52 UTC 
That is deferred to the "Fetch layer". See bug 20045. In the URL parser anything goes.
Comment 2 Ian 'Hixie' Hickson 2013-02-13 00:16:35 UTC 
Does this match implementations? Whether an error occurs at URL parse/resolve time or at fetch time affects e.g. navigation.
Comment 3 Anne 2013-02-13 07:18:29 UTC 
As per usual, the answer is in the middle. Opera and Chrome navigate. Firefox (does not even make it a link) and Safari (makes it a link, but clicking it does nothing) do not.

I prefer not inlining the data URL parser, but I can ask around a bit more first.
Comment 4 Ian 'Hixie' Hickson 2013-02-13 19:43:00 UTC 
So long as we're not going against interop, I'm happy with any solution here.
Comment 5 Anne 2013-08-19 16:22:51 UTC 
Lets leave it like this for now.