-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTML: set location.protocol to broken schemes #4412
Conversation
See whatwg/url#61 for context.
Notifying @Ms2ger, @ayg, @gsnedders, @jdm, @jgraham, @sideshowbarker, @zcorpan, and @zqzhang. (Learn how reviewing works.) |
Note: this requires some changes to the URL Standard that the HTML Standard has forever anticipated. PR coming up for that. |
This is necessary to define the behavior of the Location object’s protocol attribute, which throws on syntax errors rather than silently ignoring them as other protocol setters do. Tests: web-platform-tests/wpt#4412. This is the cleanup work mentioned in whatwg/html@f0a7365 345689 that is happening way late.
This is necessary to define the behavior of the Location object’s protocol attribute, which throws on syntax errors rather than silently ignoring them as other protocol setters do. Tests: web-platform-tests/wpt#4412. This is the cleanup work mentioned in whatwg/html@f0a7365 that is happening way late.
It might be worth testing these broken schemes inside a data URL |
whatwg/url#194 is the change to the URL Standard by the way. This is ready to land now. |
FirefoxTesting revision 1765203 All results/html/browsers/history/the-location-interface/location-protocol-setter.html
|
ChromeTesting revision 1765203 All results/html/browsers/history/the-location-interface/location-protocol-setter.html
|
These all fail in Chrome and Firefox because of the exception type, right? I think we should change it to SyntaxError DOMException in the tests and spec before merging; no need to churn browsers over this detail. |
Well Firefox needs a change anyway since it's not "SyntaxError" there but rather some internal thing. I guess we can decide to align with Chrome, but it seems a little weird since we use TypeError normally for URL parsing issues. |
See whatwg/url#61 for context. #4412 tests broken schemes.
Hmm. Edge also has a weird
|
Okay, I will give up, but not today, dinner time! |
This matches Chrome and Safari. Edge and Firefox use an internal error that needs to change either way. Tests: web-platform-tests/wpt#4412. Additional context: whatwg/url#61.
This is now ready to land. |
This matches Blink and WebKit. Edge and Gecko use an internal error that needs to change either way. Tests: web-platform-tests/wpt#4412. Additional context: whatwg/url#61.
This is necessary to define the behavior of the Location object’s protocol attribute, which throws on syntax errors rather than silently ignoring them as other protocol setters do. Tests: web-platform-tests/wpt#4412. This is the cleanup work mentioned in whatwg/html@f0a7365 that is happening way late.
See whatwg/url#61 for context. #4412 tests broken schemes.
This matches Blink and WebKit. Edge and Gecko use an internal error that needs to change either way. Tests: web-platform-tests/wpt#4412. Additional context: whatwg/url#61.
See whatwg/url#61 for context.