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
If you look at https://wpt.fyi/results/html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html%3Finclude%3Dxml and surrounding tests it's pretty clear that user agents are aligned on not always using the UTF-8 URL encoding for <?xml-stylesheet?> despite that making a lot of sense.
<?xml-stylesheet?>
At this point maybe we should admit defeat and update the specification and test expectations.
Thoughts?
cc @zcorpan @chrishtr
The text was updated successfully, but these errors were encountered:
Agreed.
Sorry, something went wrong.
No branches or pull requests
If you look at https://wpt.fyi/results/html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html%3Finclude%3Dxml and surrounding tests it's pretty clear that user agents are aligned on not always using the UTF-8 URL encoding for
<?xml-stylesheet?>
despite that making a lot of sense.At this point maybe we should admit defeat and update the specification and test expectations.
Thoughts?
cc @zcorpan @chrishtr
The text was updated successfully, but these errors were encountered: