Re: [whatwg/url] URL path shortening for ../ creates problem with other URL parsers that do not follow the whatwg standard (Issue #810)

Hi
>It's defined in the standard like this because this is how browsers have behaved for a long time. They parse and mostly-canonicalize at the same time.

Well then why even follow the whatwg standard if it's mainly focused on browsers?
Really wonder why this URL class has been made standard in NodeJs, will open a issue at NodeJs and link it here.

Btw I also opened an issue at fastify.
https://github.com/fastify/fastify/issues/5204

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

Message ID: <whatwg/url/issues/810/1872090812@github.com>