Re: [whatwg/url] IDNA / UTS #46 "should" requirements (#110)

Just an update on user-agent support from a random user who happened to Googlewhack to this thread (edit: sorry, it seems to have gone a tad off topic): 

* :white_check_mark: As mentioned by @achristensen07, WebKit seems to be using some form of non-transitional processing. It looks like this has been picked up by Safari Technical Preview as well.
* :white_check_mark: Firefox has landed this in stable at some point in 2016.
* :red_circle: Chrome's most recent ticket [505262](https://bugs.chromium.org/p/chromium/issues/detail?id=505262&thanks=505262&ts=1435488604) is currently `WONTFIX` and they might reconsider at some point in 2017.
* :red_circle: Edge hasn't had an update in a year now [6818768](https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/6818768/).

In a quick check of development environments I've used in the last 24 hours (transparent support via the language's HTTP interfaces are untested):
* :white_check_mark: Node.js has been using non-transitional IDN since has least 0.10.41 (the oldest I have installed).
* :large_orange_diamond: PHP supports since 5.4, though IDN2003 is still the (deprecated) default. One probably wants:

  ```php
  idn_to_ascii('gießen.xx', IDNA_NONTRANSITIONAL_TO_ASCII | IDNA_CHECK_BIDI | IDNA_CHECK_CONTEXTJ, INTL_IDNA_VARIANT_UTS46);
  ```
* :white_check_mark: In Go, `golang.org/net/x/idna` does non-transitional processing.  Interestingly, the support in the `github.com/miekg/dns/idn` package also does non-transitional processing for the inputs I've tested, despite the documentation saying it implements IDN2003.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/110#issuecomment-284941364