Re: [whatwg/url] javascript: URL parsing (#307)

Yeah, Chromium had a lot of javascript URL parsing changes a couple of years ago. I believe that is now fully aligned with the HTML spec, but of course the URL parser itself is not aligned yet.

I think failing to parse in the URL parser is the best idea. Unfortunately, the non-special URL parsing in Chrome still doesn't actually parse apart authority and path.

I'm not sure why WebKit behaves differently between `new URL()` and `<a href>` though – I presume the latter uses a different parser for `javascript:` URLs?

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

Message ID: <whatwg/url/issues/307/1458387568@github.com>