- From: Anne van Kesteren <notifications@github.com>
- Date: Sun, 05 Mar 2023 10:15:30 -0800
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 5 March 2023 18:15:43 UTC
I tried to go through this again: * @domenic's original example is now interoperable between WebKit and Chromium, but requires a new Live URL Viewer URL: https://jsdom.github.io/whatwg-url/#url=amF2YXNjcmlwdDp3aW5kb3cubG9jYXRpb24ucmVwbGFjZSgiaHR0cHM6Ly93aGF0c29ldmVyLmNvbS8/YT1iJmM9NSZ4PXkiKQ==&base=YWJvdXQ6Ymxhbms= * @zcorpan's examples still show a difference https://jsdom.github.io/whatwg-url/#url=amF2YXNjcmlwdDovL3Rlc3Q6dGVzdC8lMGFhbGVydCgxKQ==&base=YWJvdXQ6Ymxhbms= errors in WebKit, but not Chromium. And http://software.hixie.ch/utilities/js/live-dom-viewer/saved/5134 alerts in both WebKit and Chromium. If you inject `	` into the scheme of the latter example you get some kind of error in WebKit, but Chromium still shows the alert. I think ideally we fix these cases by failing to parse, as WebKit already does in `new URL()`. Thoughts? I'm happy to add the relevant tests. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/url/issues/307#issuecomment-1455163759 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/url/issues/307/1455163759@github.com>
Received on Sunday, 5 March 2023 18:15:43 UTC