Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)

On Wed, 2016-05-11 at 15:12 -0700, Gregory Wild-Smith wrote:
> > 
> > Web content in the wild is already broadly not spec-compliant
> While true in this particular issue they wouldn't work in Safari or
> on iOS at all... as that is not the case this  shows that to be not
> true in that particular instance.
> 
> Also given that as you say....
> 
> > 
> > The WHATWG URL spec is designed to standardize URL parsing in HTML
> > tags and HTTP headers
> Then thinking about it from a browser-only perspective (as the
> comments here appear to) is specifically *against the design of the
> spec* as many other things consume HTTP headers. Not just browsers.

There is also the issue that, if this is about HTTP headers alone, it
shouldn't be a "URL Standard", it should be "HTTP URL Standard" or
"Browser URL Standard", both of which show that this has very little to
do with URLs and more to do with how browsers handle them.


---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/118#issuecomment-218641399