Re: [whatwg/url] Initialize the IgnoreInvalidPunycode flag when calling UTS 46 (Issue #821)

AFAICT, the current behavior of Firefox and Safari would be consistent with setting this flag to `false` and Chrome’s behavior would be consistent with setting this flag to `true`.

Looking at how browsers comply with the existing spec, Safari seems to comply well, Firefox seems to comply except Firefox fails to enforce bidi rule on LTR labels in a bidi domain name (i.e. Firefox enforces the bidi rule on a per-label basis), and Chrome’s behavior seems hard to explain from the spec.

These observations would support setting `IgnoreInvalidPunycode` to `false`. However, I’m missing some context of why the `IgnoreInvalidPunycode` flag was introduced in UTS 46. The rationale says it enables an ASCII fast path, but UTS 46 still requires validating `xn--` labels that decode successfully as Punycode, so the flag does not, AFAICT, enable an ASCII fast path in general (and the “industry practice” evidently doesn’t cover Firefox and Safari).

@markusicu, @macchiati, can you share more context for the motivation of `IgnoreInvalidPunycode` and how you’d expect the URL Standard to set the flag?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/821#issuecomment-1973116108
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/821/1973116108@github.com>