- From: Henri Sivonen <notifications@github.com>
- Date: Thu, 28 Nov 2024 00:32:16 -0800
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 28 November 2024 08:32:20 UTC
@socram8888 , As for the validation step: The validation step needs to prohibit unassigned code points when going from the Unicode form to the ASCII form, because their future normalization behavior isn't known and the operation depends on normalization. If labels that are already in the ASCII form weren't subject to validation, round-trippability between the ASCII and Unicoode forms wouldn't be stable. This does have the side effect that domains from the future don't work in old software, but that's not too much of a practical problem in browsers due to the update cycle. (The update cycle isn't immediate. E.g. Firefox's IDNA is on Unicode 15.1 instead of 16.0 right now, but it's not unbounded waiting.) In any case, you are asking for a design change to IDNA that doesn't belong in the URL Standard. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/url/issues/821#issuecomment-2505532331 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/url/issues/821/2505532331@github.com>
Received on Thursday, 28 November 2024 08:32:20 UTC