Re: [whatwg/url] Refusing a mix of numeric-only and BIDI domains (#543)

My plan is to submit feedback to Unicode's April meeting to get this addressed. Draft:

> Please change the processing model of _CheckBidi_ to allow for more right-to-left domains.
>
> Currently when _CheckBidi_ is set to true and the input is determined to be a _Bidi domain name_ it enforces all six subrules of The Bidi Rule https://www.rfc-editor.org/rfc/rfc5893.html#section-2 for each label of a domain. This has a couple of issues:
>
> * As discussed in https://github.com/whatwg/url/issues/543 subrule 1 alone ends up disallowing EN code point labels in such domain names (e.g., `1.ي` is a fatal error). This seems unnecessarily constraining.
> * Subrule 1 also creates undefined behavior for empty string labels (e.g., for a domain such as `ي.`), as it imposes requirements upon a character that is not there. (If the expectation is that trailing dots are removed before ToASCII is invoked that could use clearer documentation or an assert somewhere.)
> * As discussed in the URL Standard issue referenced one of the editors of IDNA2008 asserts The Bidi Rule was not aimed at client implementations, but rather at registries. While browsers have been enforcing it to varying degree nevertheless as suggested by UTS46, it's probably worth another close review to ensure this is actually what we want.
>
> I don't have a recommendation here unfortunately as this is not my area of expertise. It's my hope Bidi experts on the committee can help out. One solution might be to not enforce subrule 1 for left-to-right labels, but do enforce that a label that starts with an EN code point cannot follow a right-to-left label. 

If anyone here has suggestions for how to make this more concrete I'm all ears.

cc @ricea

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/543#issuecomment-1384153410

You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/543/1384153410@github.com>