I'm on Mozilla's Policy Advisory Board, if you want me to try to escalate it. We just need to narrow things down to a simple, discrete ask.

Christian Dawson
Executive Director
Internet Infrastructure Coalition (i2C)
c:  703 623 2612
http://i2coalition.com

PGP: 22DF5493
Fingerprint: 7C95 A3BE 1E10 4864 8417  DCED B9E1 C8FD 22DF 5493

On Aug 31, 2017, at 3:50 PM, Don Hollander <don.hollander@icann.org> wrote:

We did have some engagement with Mozilla facilitated by Jothan.  But their response was for us to file a bug report.   

Don


On 1/09/2017, at 12:27 AM, chaals is Chaals McCathie Nevile <chaals@yandex.ru> wrote:

On Thu, 31 Aug 2017 02:18:54 +0200, Don Hollander <don.hollander@icann.org> wrote:


04a – A review of popular browsers for UA Readiness – Spoiler alert – most are OK, but few >handle the open dot or IDNs as we expect them to.   Some browser developers may see this >as a feature and not a bug.


The document says there is no W3C document talking about open dot. I am pretty sure you are right about that - in general W3C defers to IETF RFCs for URL definitions, having abandoned its own work on them a few years ago.

The reference for Mozilla seems to have been unchanged in 8 years, which is a long time. Do you know if anyone at Mozilla has actually looked at the issue since then? In particular, I tried changing the settings as described there, to allow the open dot, and it didn't.

cheers


--
Chaals is Charles McCathie Nevile
find more at http://yandex.com

Don Hollander
Universal Acceptance Steering Group
Skype: don_hollander