- From: <bugzilla@jessica.w3.org>
- Date: Thu, 03 Apr 2014 13:02:25 +0000
- To: www-international@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24845 Henri Sivonen <hsivonen@hsivonen.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bzbarsky@mit.edu --- Comment #5 from Henri Sivonen <hsivonen@hsivonen.fi> --- (In reply to Simon Pieters from comment #4) > Consider a document (with a http: base URL) with encoding windows-1251 which > includes a link <a href="?å"> and a form <form><input name=x > value="å"></form>. å is not representable in windows-1251. The former > is turned into ?%3F and the latter is turned into ?%26%23229%3B. The > proposal is to make both ?%26%23229%3B. > > The proposal matches WebKit/Blink. > > IE almost matches the current spec, it just doesn't percent-escape the "?". I could live with matching WebKit/Blink. The probability of IE's approach ever leading to a useful URL seems low. > Gecko switches to utf-8 for the whole URL and gets ?%C3%A5. Hmm. Switching the encoding when one non-representable character is added doesn't seem like a good idea to me, especially if other browsers don't do the same. CCing bz in the hope of getting background info. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Thursday, 3 April 2014 13:02:26 UTC