This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
See bug 23968 which is the same issue but for CSS. As for the url query encoding situation in impl, it's as follows: d.e. = document's encoding Element Gecko Blink Presto a d.e. d.e. d.e. feImage d.e. ? utf-8 image d.e. utf-8 utf-8 use d.e. d.e. utf-8 (IE not tested.) HTML uses the document's encoding for almost everything. It's unclear whether we should be consistent or use utf-8 as much as possible. Hixie argues for the former.
Do you mean the URL spec of the WHATWG? Read the latest status document (as far as I know) about stability of normative references (which we need here). I do not think that the WHATWG spec currently fulfills the criteria.
The WHATWG URL standard is more stable than any W3C or IETF reference on the subject... (and more importantly, more accurate, too)
(In reply to Ian 'Hixie' Hickson from comment #2) > The WHATWG URL standard is more stable than any W3C or IETF reference on the > subject... (and more importantly, more accurate, too) That is great! And still the specification changes nearly everyday and does not fulfill the requirements of the W3C. Which would not be a problem at all, unless you actually want a W3C spec to get a REC at some point. Would there be daily (but of course then outdated) snapshots that can be referenced, the requirement would be fulfilled and we can finally reference WHATWG specs.