- From: Anne van Kesteren <notifications@github.com>
- Date: Tue, 10 Jan 2023 06:15:21 -0800
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 10 January 2023 14:15:33 UTC
This might also be more complicated still as, e.g., `يa` is rejected by all browsers. Which I think is due to mixing L and R character properties and would not be rejected without CheckBidi being true? And then `1.ي` is only rejected in Chromium and WebKit. So Chromium can again be explained through an erroneous ASCII fast path. And it seems that Gecko has a different CheckBidi behavior when it comes to ASCII digits at least, perhaps due to the above contradiction. Or perhaps there is another check related to character properties unrelated to CheckBidi. (All of this is only concerned with the ToASCII code path, for what it's worth.) -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/url/issues/543#issuecomment-1377347000 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/url/issues/543/1377347000@github.com>
Received on Tuesday, 10 January 2023 14:15:33 UTC