Re: [whatwg/url] URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true (Issue #784)

karwa left a comment (whatwg/url#784)

One interesting thing about how these URLs currently behave is that, even though they have spaces, the spaces are only left unescaped in the path - checking them in JSDOM, spaces in the query and fragment are escaped as usual. So they are even more awkward than they first look.

```
[Original] javascript:"%252525 ? %252525 # %252525"
[Parsed]   javascript:"%252525 ?%20%252525%20#%20%252525%22
```

It's unfortunate because the consumers of these URLs clearly are able to handle escaped spaces. But we have to leave them unescaped for compatibility with other things, which is what leads to this requirement to trim in the first place.

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

Message ID: <whatwg/url/issues/784/2703684896@github.com>