We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently all JS engines behave differently when it comes to hosts with custom protocols: https://felixfbecker.github.io/whatwg-url-custom-host-repro/
What is the correct behavior?
The text was updated successfully, but these errors were encountered:
whatwg-url and Node generally match the standard (at least the tests). Safari is close.
Sorry, something went wrong.
So just to confirm, a bug needs to be filed for Chrome, Firefox, Edge and Safari?
Is there a test in the test suite for this?
I know Chrome, Edge, and Firefox at least have a general "implement the URL standard" bug. It might be worth filing more specific bugs though.
I'm pretty sure this is tested, e.g., sc://faß.ExAmPlE/ in https://github.com/web-platform-tests/wpt/blob/master/url/resources/urltestdata.json.
sc://faß.ExAmPlE/
No branches or pull requests
Currently all JS engines behave differently when it comes to hosts with custom protocols: https://felixfbecker.github.io/whatwg-url-custom-host-repro/
What is the correct behavior?
The text was updated successfully, but these errors were encountered: