Re: [whatwg/url] Parser generates invalid URLs (#379)

alwinb left a comment (whatwg/url#379)

I've separated two out. But would you like me to create a third issue for the following?

> Can we have a look at this issue again, where we do not consider opaque paths? Because then the discrepancy between valid and parser-produced is much (much!) smaller and can potentially be bridged.

That one seems to purely be a follow-up to this thread.

***
Specifically, if we do not consider opaque paths we have to reconsider validity of:

- `#` in fragment
- `"` in opaque host
- The backtick ` in opaque host and query
- `[ \ ] | ^` in path components, query and fragment
- `{ }` in opaque host, query and fragment

All these are considered invalid; but are not percent encoded, causing the invalidity to leak into the parser output.

As for `[]` there is a proposal #753 to consider them valid already. 
As for `\` in path components, this can only happens in non-special URLs. 

Note that this would not need any change to the parser, it is merely a question of what we call valid versus invalid. Or perhaps, valid versus  potentially unwise to use :D

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

Message ID: <whatwg/url/issues/379/2660830354@github.com>