You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Back in 2018 I worked on web-platform-tests/wpt#10891 and I didn't really question whether this is something we wanted to change, but both Chrome and Safari getting away with not passing on the document encoding (and thus using UTF-8) makes me wonder if we should just align on that instead as it's slightly simpler and requires less engines to change.
Good question. It definitely prefer UTF-8.
If Chrome & Safari have been able to get away with it, I think it's a very niche use case, and we can probably align with that.
annevk
added a commit
to web-platform-tests/wpt
that referenced
this issue
Sep 22, 2022
Back in 2018 I worked on web-platform-tests/wpt#10891 and I didn't really question whether this is something we wanted to change, but both Chrome and Safari getting away with not passing on the document encoding (and thus using UTF-8) makes me wonder if we should just align on that instead as it's slightly simpler and requires less engines to change.
@valenting thoughts?
Related bugs:
The text was updated successfully, but these errors were encountered: