Currently encoding the query component of a URL using the document's encoding affects all URLs with a "relative scheme" (http/ws/file/...). Should we restrict this to http/https/file so new schemes such as ws/wss and others will not be affected by this weird legacy quirk? Is that something implementors would consider following?
The parsing section of http://url.spec.whatwg.org/ has this as an open issue for now. -- http://annevankesteren.nl/
