Simon Says wrote on Apr 12, 2020, 05:47:
eRe4s3r wrote on Apr 12, 2020, 04:31:
That's completely irrelevant... Bluesnews uses this
while the correct method is this
<html lang="en><meta charset="utf-8">
or in complex layouts this
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
Lack of meta charset setting before loading the css means brave will auto-detect it based on site content and get it wrong depending on what it finds first.... point is, change the default for this website in your browser
Still doesn't tell me why it was ok yesterday and today it's wonky or how to fix it on Brave. I browsed all the settings, advanced and every submenu, didn't find anything about changing unicode and co.
Quick google search didn't help either. Heh, nvm, It's still readable until Frans fixes it on the site's end.
Cheers, ty anyway.
Well sometimes you can fix things.. and sometimes Brave removed the feature to select custom encoding a few months ago because Chromium removed the feature a few months ago, and to be clear, Google
removed the feature from Chromium
So yeah, you can't fix it in Brave. That was news to me too.