It seems to omit discussion of query, which has the most historical baggage due to encodings coming into play.
The infinite number of slashes is only a thing for special URLs. So it doesn't affect all URLs.
86 doesn't say it's the first @. It simply disallows multiple @ and it's only error handling is that you fail parsing altogether if you find multiple.
The URL Standard also only considers 86 IPv4 addresses as valid, but it parses more variants.
IDNA: we already discussed this. The UTS 46 ToASCII algorithm defines how they work (though there are some issues as you can find in the URL repository).
The URL Standard actually restricts ports to a 16-bit integer. That's different from 86 which has no such restriction.
Apart from space there's a number of ASCII code points that are parsed in the URL Standard whereas 86 would reject. That's true for most components I think.
E.g., you say there's no issues with fragments, but currently Firefox encodes spaces there, but other browsers do not. Or did you mean to limit this to issues that affect network protocols?
It seems to omit discussion of query, which has the most historical baggage due to encodings coming into play.
The infinite number of slashes is only a thing for special URLs. So it doesn't affect all URLs.
86 doesn't say it's the first @. It simply disallows multiple @ and it's only error handling is that you fail parsing altogether if you find multiple.
The URL Standard also only considers 86 IPv4 addresses as valid, but it parses more variants.
IDNA: we already discussed this. The UTS 46 ToASCII algorithm defines how they work (though there are some issues as you can find in the URL repository).
The URL Standard actually restricts ports to a 16-bit integer. That's different from 86 which has no such restriction.
Apart from space there's a number of ASCII code points that are parsed in the URL Standard whereas 86 would reject. That's true for most components I think.
E.g., you say there's no issues with fragments, but currently Firefox encodes spaces there, but other browsers do not. Or did you mean to limit this to issues that affect network protocols?