This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Currently, the media type is described as two monolithic algorithms, defining encoding/decoding. This makes it hard to re-use outside HTML, and also conflates issues related to HTML forms (special form parameters and types) with the actual media type format.
This bug was cloned to create bug 17889 as part of operation convergence.
Julian: any opinion on https://www.w3.org/Bugs/Public/show_bug.cgi?id=17889 ?
(In reply to comment #2) > Julian: any opinion on https://www.w3.org/Bugs/Public/show_bug.cgi?id=17889 ? Sounds a bit like wishful thinking; it's used all over the place, for instance in OAuth.
Doesn't affect UA behavior and no indications of support for making any changes here. I think we should move this to resolved=wontfix rather than leaving it hanging open with no action for another N years.
HTML5.1 Bugzilla Bug Triage: Won't Fix The noted algorithms are still there and they are still monolithic. See: http://w3c.github.io/html/sec-forms.html#urlencoded-form-data I think the note at the top conveys a warning of the inherent complexity involved. If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!