New "URL" content area?

[Josh-Cena]

We don't have a central place for documenting how browsers handle URLs:

• Text fragments lives outside of everything else
• URL fragments that represent element IDs are undocumented (I think)
• data: lives in HTTP/Basics_of_HTTP/Data_URLs
• blob: is "documented" in API/URL/createObjectURL_static (one page links there; other pages link to API/Blob which makes even less sense)
• javascript: is entirely undocumented: Content suggestion: javascript pseudo-protocol identifier content#7143, despite its many interesting behaviors
• sms:, mailto:, et al. only get a passing reference on the <a> page

The fragment affects navigation behavior, while the different schemes affect many things, including link targets, fetch, import etc. The URL API exposes the syntax of URLs, such as resolving relative references (mdn/content#33455), but not the semantics like what should happen when fetching a javascript: URI. Moreover, I think it's just "wrong" to put things like resource URI concepts under the HTTP docs, because HTTP is just a protocol, and is not the whole network. Therefore it doesn't seem right to put docs about browsers' handling of URLs anywhere. Maybe we should consider a new "URL" area under Web/?