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
WPT test html/semantics/scripting-1/the-script-element/script-charset-02 tests out various things that the <meta charset=> tag should do, and none of them are happening. Charsets do exist and can be selected other ways, but the meta tag isn't doing it in this test.
The text was updated successfully, but these errors were encountered:
It looks like every WPT test in html/syntax that tries to get to a non-utf8 charset via a meta tag, either charset or http-equiv, fails by staying in utf8.
pshaughn
changed the title
meta charset="windows-1250" seems to do nothing
meta charset and meta equiv="Content-Type" seem unable to switch away from UTF-8
Dec 3, 2019
Since this needs to happen very early during parsing, and not via DOM, it is probably not dependent on whether http-equiv is commented out in the IDL; charset isn't even in the IDL and is supposed to work.
WPT test html/semantics/scripting-1/the-script-element/script-charset-02 tests out various things that the
<meta charset=>
tag should do, and none of them are happening. Charsets do exist and can be selected other ways, but the meta tag isn't doing it in this test.The text was updated successfully, but these errors were encountered: