Re: [whatwg/url] Definition of "valid opaque-host string" contradicts parser (#437)

FWIW I think in general it is quite unlikely that the valid URL string definitions correspond precisely to the parse errors in the parser algorithm. There's no mechanism for enforcing that and it's too easy for them to get out of sync.

A to-do I've had for some time is to write an implementation that checks URLs via the parser and its parse error steps, a separate implementation that checks them via the valid URL string definitions, and then a fuzzer that generates tons of input in order to find where they differ.

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