Ticket #40 (new defect)
Implementation advice on creating IRI query strings from HTML forms
|Reported by:||email@example.com||Owned by:|
The percent-encoding handling of query components in the HTTP scheme is really unfortunate. There is no good normative advice to give if the percent-encoding is delayed until the query-IRI is interpreted. Could HTML ask browsers to percent-encode the form data using the document character set BEFORE the query IRI is constructed, and only in the case where the document character set isn't Unicode-based and the query is being added to http: or https: URIs? This would give more consistent results. Browsers might have to change their behavior in constructing the IRI-with-query-added, but the results would be more consistent and fewer bugs, and it wouldn't affect interpretation of any existing web pages. It would remove the need to have a normative special case for queries in HTML documents, just for http, in a way in which things like transcoding etc. wouldn't work well. You could tell the difference between a query URI in the address bar and one created via a form because the address bar would always be UTF-8. The browsers might have to change the algorithm for showing the address in the adress bar to know how to undo the encoding.