- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Thu, 21 Mar 2013 14:40:40 -0400
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: whatwg <whatwg@whatwg.org>
On Thu, Mar 21, 2013 at 2:33 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 3/21/13 7:01 AM, Anne van Kesteren wrote: >> as the Unicode form is very much a UI decision and >> we do not want to leak that detail to web developers. > > You mean the decision as to when exactly to use the Unicode and when to use > ACE? In what way is it a UI decision (apart from browser URL bars having > anti-phishing logic that falls back to ACE when they detect "weird" chars in > the URI)? E.g. Chrome only shows Unicode if they have indication (prolly locale) that the end-user will understand it and will use ACE otherwise. I do not want that kind of logic to leak through developer-exposed APIs. That's madness. See http://wiki.whatwg.org/wiki/URL#UI for links to more details. > Or put another way, it seems like we should be trying to use IRIs until we > can't for some reason, and I see no a priori reason that location.href can't > be an IRI... If we can define "until we can't" I would be okay with that. Otherwise it seems safer to always use punycode and delegate the problem. -- http://annevankesteren.nl/
Received on Thursday, 21 March 2013 18:41:12 UTC