Bug 230051 - Compat problem with new URL()
Summary: Compat problem with new URL()
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Platform (show other bugs)
Version: Safari 14
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2021-09-08 09:59 PDT by Luke Warlow
Modified: 2021-09-15 10:19 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Luke Warlow 2021-09-08 09:59:23 PDT 
Steps to reproduce the problem:
1. Navigate to https://jsfiddle.net/40abpv7d/
2. Look at the HTML output


I'm not entirely sure on the correct behaviour. Chrome, Firefox and Safari all behave differently.

Chrome - https://%22google.com/
Safari - https://"google.com/
Firefox - TypeError: URL constructor: https://"google.com is not a valid URL.


As I say I'm not sure if Chrome, Firefox or Safari is "correct" as far as the spec is concerned. But from what I as a web developer expect I would say that Firefox is the most correct, followed by Chrome. Safari's behaviour of outputting a non URL safe string surprises me.
Comment 2 Radar WebKit Bug Importer 2021-09-15 10:00:22 PDT 
<rdar://problem/83155604>
Comment 3 Alex Christensen 2021-09-15 10:19:51 PDT 
According to https://url.spec.whatwg.org/#forbidden-host-code-point WebKit is correct here.  I look forward to other browsers either changing to match the spec or raising an issue with the spec for discussion.  It seems like Firefox intends to match the spec here.