Re: [whatwg/url] Should we unescape characters in path? (#606)

Also reading #369 again, it has an especially good description. That issue also explains the address bar behaviour of Firefox.  

My take is that we have to make a decision about how to handle invalid escape sequences. Not knowing/ deciding on how to handle those leads to the current situation by default rather than by making a deliberate decision. And if it ends up not being used by browsers, then it is still valuable to specify a recommended behaviour for other applications.  

To move on with https://github.com/whatwg/url/issues/606#issuecomment-930109895, I think it is needed. And I think we have to revisit the reserved characters. Unless we’d go for a comparison on URL records with fully decoded components. But I’m not sure that is desirable, especially in the query string. 

-- 
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/606#issuecomment-950297413