230051 2021-09-08 09:59:23 -0700 Compat problem with new URL() 2021-09-15 10:19:51 -0700 1 1 1 Unclassified WebKit Platform Safari 14 Unspecified Unspecified RESOLVED INVALID InRadar P2 Normal --- 1 lwarlow webkit-unassigned achristensen ap webkit-bug-importer oldest_to_newest 1791510 0 lwarlow 2021-09-08 09:59:23 -0700 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. 1791511 1 lwarlow 2021-09-08 09:59:46 -0700 Firefox Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1729733 Chrome Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1247709 1793737 2 webkit-bug-importer 2021-09-15 10:00:22 -0700 <rdar://problem/83155604> 1793745 3 achristensen 2021-09-15 10:19:51 -0700 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.