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
{ 0xe2, 0x8e, 0x8c } (can be interpreted as “⎌” or as “⎌”)
{ 0xe2, 0x9d, 0x8f } (can be interpreted as “â��” or as “❏”)
{ 0xe2, 0x96, 0xbd } (can be interpreted as “â–½” or as “▽”)
Obviously, the administrator of this website SHOULD be declaring his encoding (whether it be UTF-8 or Windows-1252). But, given that he hasn't, is Edge's behavior here at least ALLOWABLE?
The text was updated successfully, but these errors were encountered:
Actually, on further testing, Edge's behavior here is intermittent, and it switched to UTF-8 permanently after I loaded the CSS file's URL in its own document tab (presumably something to do with cached auto-detection?)
[source] (https://www.w3.org/International/questions/qa-css-charset) [en]
Is there any official guidance on how browsers should interpret CSS documents that lack any encoding declaration?
For example, the latest version [117.0.2045.47] of Microsoft Edge yields mojibake when rendering this page: https://www.devever.net/~hl/omi
<meta>
tag{ 0xe2, 0x80, 0x93 }
(can be interpreted as “–” or as “–”){ 0xc2, 0xb7 }
(can be interpreted as “·” or as “·”){ 0xe2, 0x8f, 0xa9, 0xef, 0xb8, 0x8e }
(can be interpreted as “â�©ï¸Ž” or as “⏩︎”)[*The latter includes U+FE0E Variation Selector 15, which is supposed to make it display in its non-Emoji form.]
{ 0xe2, 0x8e, 0x8c }
(can be interpreted as “⎌” or as “⎌”){ 0xe2, 0x9d, 0x8f }
(can be interpreted as “â��” or as “❏”){ 0xe2, 0x96, 0xbd }
(can be interpreted as “â–½” or as “▽”)Obviously, the administrator of this website SHOULD be declaring his encoding (whether it be UTF-8 or Windows-1252). But, given that he hasn't, is Edge's behavior here at least ALLOWABLE?
The text was updated successfully, but these errors were encountered: