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

I don't know what your definition of "the web" is, but the web goes far beyond the HTTP protocol.

On May 11, 2016 10:32:51 PM EDT, "Jasper St. Pierre" <notifications@github.com> wrote:
>WHATWG stands for the "Web Hypertext Application Technology Working
>Group". It's implicit that any standards released by them are primarily
>in the context of the web, especially people implementing web browser
>technologies.
>
>Explicit language to make this clearer in the spec is, of course,
>welcome, especially now that more eyeballs are on the spec it given
>Daniel's blog post today. But, again, this spec is about how
>invalid-by-RFC-terms URLs found on the web should be parsed and the
>interpretations they should have. Outside of web contexts, especially
>when generating new URLs in your own cases, you are welcome and
>recommended to use RFC 3986.
>
>As for "Safari and iOS don't support it", the obvious answer is "yet".
>WebKit has bugs open about implementing the URL spec, and for web
>compatibility they will eventually move to the new spec'd parsing
>algorithm. That said, the error case for someone using an (arguably)
>niche browser is that they get an error message which is easy to
>dismiss and pass off as "oh, the internet isn't working today".
>
>---
>You are receiving this because you were mentioned.
>Reply to this email directly or view it on GitHub:
>https://github.com/whatwg/url/issues/118#issuecomment-218644103

-- 
John M. Harris, Jr.
PGP Key: f2ea233509f192f98464c2e94f8f03c64bb38ffd

Sent from my Android device. Please excuse my brevity.


---
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-218645043