Re: nsIURI API changes - punycode domain names

2017-08-10 Thread Anne van Kesteren
On Wed, Aug 9, 2017 at 8:37 PM, Boris Zbarsky wrote: > On 8/9/17 1:43 PM, Daniel Veditz wrote: >> >> What do web pages do if they want to reflect a pretty URL into their page? > > Cry, basically. I have a proposal: https://github.com/whatwg/url/pull/288. There's two issues:

Re: nsIURI API changes - punycode domain names

2017-08-09 Thread Boris Zbarsky
On 8/9/17 1:43 PM, Daniel Veditz wrote: ​What do web pages do if they want to reflect a pretty URL into their page? Cry, basically. This is the fundamental reason I was opposed to this behavior change, but apparently no other browsers care about this issue and we were getting compat

Re: nsIURI API changes - punycode domain names

2017-08-09 Thread Valentin Gosu
On 9 August 2017 at 19:43, Daniel Veditz wrote: > On Wed, Aug 9, 2017 at 9:57 AM, Valentin Gosu > wrote: > >> This is a definite improvement in terms of web-compat. document.origin, >> location.href, etc will from now on return punycode. >> > >

Re: nsIURI API changes - punycode domain names

2017-08-09 Thread Daniel Veditz
On Wed, Aug 9, 2017 at 9:57 AM, Valentin Gosu wrote: > This is a definite improvement in terms of web-compat. document.origin, > location.href, etc will from now on return punycode. > ​What do web pages do if they want to reflect a pretty URL into their page? Will

nsIURI API changes - punycode domain names

2017-08-09 Thread Valentin Gosu
TL;DR: we have made some changes to the nsIURI API that affect IDN domain names Before: ASCII - GetAsciiSpec, GetAsciiHost, GetAsciiHostPort UTF-8 - GetSpec, GetPrePath, GetHost, GetHostPort Now: UTF-8 - GetDisplaySpec, GetDisplayPrePath, GetDisplayHost, GetDisplayHostPort ASCII