3 ms·
The "without meta utf-8" part of course depends on your browser's default encoding.
by isolay 11mo ago
The "without meta utf-8" part of course depends on your browser's default encoding.
- kevin_thibedeau 11mo agoWhat mainstream browsers aren't defaulting to utf-8 in 2025?
- naniwaduni 11mo agoAll of them, pretty much.
- akho 11mo agohtml5 does not even allow any other values in <meta charset=>. I think you need to use a different doctype to get what the screenshot shows.
- layer8 11mo agoWhile true, they also require user agents to support other encodings specified that way: https://html.spec.whatwg.org/multipage/parsing.html#character-encodings https://html.spec.whatwg.org/multipage/parsing.html#characte... Another funny thing here is that they say “but not limited to” (the listed encodings), but then say “must not support other encodings” (than the listed ones).
- shiomiru 11mo agoIt says > the encodings defined in Encoding, including, but not limited to where "Encoding" refers to https://encoding.spec.whatwg.org https://encoding.spec.whatwg.org (probably that should be a link.) So it just means "the other spec defines at least these, but maybe others too." (e.g. EUC-JP is included in Encoding but not listed in HTML.)
- layer8 11mo agoAh, I understood it to refer to encoding from the preceding section.
- layer8 11mo agoI wouldn’t be surprised if they don’t for pages loaded from local file URIs.
- Eric_WVGG 11mo agoI spent about half an hour trying to figure out why some JSON in my browser was rendering è incorrectly, despite the output code and downloaded files being seemingly perfect. I came to the conclusion that the browsers (Safari and Chrome) don't use UTF-8 as the default renderer for everything and moved on. This should be fixed, though.