-
Notifications
You must be signed in to change notification settings - Fork 133
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
Use HTML's parse a URL #380
Comments
It seems we already standardized on that https://xhr.spec.whatwg.org/#dom-xmlhttprequest-open and it's just the test expectations that are wrong. Hmm. Oh well, I guess all the refactoring of HTML was good anyway. |
annevk
added a commit
that referenced
this issue
Sep 19, 2023
annevk
added a commit
that referenced
this issue
Sep 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As https://wpt.fyi/results/html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html%3Finclude%3Dxhr and surrounding tests indicate all implementations are aligned on not always using UTF-8 as the URL encoding. Given this is an old API it's probably better to standardize on that and change the test expectations.
The text was updated successfully, but these errors were encountered: