Repository navigation
canonicalize an opaque pathname is broken #267
Description
What is the issue with the URL Pattern Standard?
"opaque path state" is not a supported state override. It won't encode ? and # for instance.
This needs some amount of rethinking. And tests I guess.
It's also pretty broken that this is used for all non-special URLs. Not all non-special URLs have an opaque path. Not sure to what extent that can still be remedied.
Activity
sisidovski commentedon Apr 4, 2025
Could you elaborate on a bit more about "opaque path state" is not a supported state override? Are you saying we cant set opaque path state as a state override to invoke the basic url parser?
annevk commentedon Apr 4, 2025
Correct, it doesn't expect to be invoked as such at all. (I mentioned some of the things that go wrong in OP, such as
?switching states instead of getting encoded.)