- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Mon, 21 Nov 2016 09:39:08 +0100
- To: Mark Davis ☕ <markdavis@google.com>
- Cc: www-archive <www-archive@w3.org>, Sebastian Mayr <github@smayr.name>
Hi Mark, As you might recall we track IDNA issues that affect the URL Standard through https://github.com/whatwg/url/issues/53. The last set of feedback was recorded here http://www.unicode.org/review/pri317/ and apparently closed without it being addressed. Could you perhaps shed some light on that? Somewhat related, now both Firefox and Safari use Nontransitional_Processing (i.e., IDNA2008), which for now is still against the URL Standard as that requires Transitional_Processing, but I think the time has come to change that. The commit message at https://trac.webkit.org/changeset/208902 is pretty detailed on the specifics. It turns out that some of the implemented processing steps are SHOULD-level requirements in UTS46. I think these should be refactored to be options for the ToASCII and ToUnicode algorithms, so the URL Standard can enforce them. It does not seem great to allow variable processing. Kind regards, -- https://annevankesteren.nl/
Received on Monday, 21 November 2016 08:39:38 UTC