Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703)

> But being generous to writers who type in URLs by hand into HTML and the Address bar isn't worth the pain of making every other non-browser application suffer.

Then again, it appears that many non-browser applications deviate from the RFCs specifically to adopt lenient parsing behaviour from the web, as it can emerge in unexpected places. HTTP redirects, for instance, seem to come up often as a place where people see dodgy URLs/relative references.

So I'm not really sure that it is fair to characterise web-compatibility as "pain" and "suffering"; non-browser applications seem to be willingly adopting these behaviours, at the request of their users, even before there was a formal standard telling them what web-compatibility even meant.

For most modern browsers, input in to the address bar goes through a totally different "fixup" process which considers things like the user's history and bookmarks, automatically adds schemes, adds TLDs to domains (e.g. `.com`), and lots of other stuff. It has nothing to do with anything in this standard -- and the standard in fact [calls it out](https://url.spec.whatwg.org/#url-parsing) as being out-of-scope:

> How user input in the web browser’s address bar is converted to a URL record is out-of-scope of this standard.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/703#issuecomment-1243062167

You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/703/1243062167@github.com>