IDNA: avoid defining valid domain string in terms of the parser #245

annevk · 2017-02-10T15:29:46Z

This is basically something we need to raise again with the IDNA folks as their document does not really address it. This used to be tracked by https://www.w3.org/Bugs/Public/show_bug.cgi?id=25334.

As part of fixing this we should make it clear they are at least ASCII case-insensitive.

annevk added topic: idna non-normative and removed non-normative labels Feb 10, 2017

annevk added the i18n-tracking label Oct 13, 2017

karlcow mentioned this issue Oct 18, 2018

URL requirement on the form accepts URL with a space in the domain name webcompat/webcompat.com#2662

Closed

himorin mentioned this issue Nov 12, 2019

IDNA: avoid defining valid domain string in terms of the parser w3c/i18n-activity#816

Open

annevk removed the i18n-tracking label Nov 21, 2019

annevk added i18n-tracker topic: model topic: validation and removed topic: model labels May 4, 2020

annevk mentioned this issue May 5, 2020

case-insensitive domain names #357

Closed

This comment was marked as spam.

Sign in to view

whatwg / url

IDNA: avoid defining valid domain string in terms of the parser #245

IDNA: avoid defining valid domain string in terms of the parser #245

annevk commented Feb 10, 2017 •

edited

This comment was marked as spam.

whatwg / url

IDNA: avoid defining valid domain string in terms of the parser #245

IDNA: avoid defining valid domain string in terms of the parser #245

Comments

annevk commented Feb 10, 2017 • edited

This comment was marked as spam.

annevk commented Feb 10, 2017 •

edited