(In reply to ersatzemail from comment #2) > It was actually a local file; Could you please [attach the file](https://bugzilla.mozilla.org/attachment.cgi?bugid=1615836&action=enter)? Feel free to edit it beforehand, as long as there's enough content left to reproduce the problem. > in fact it occurs in many similar files I used Notepad to save the attached testcase as ANSI, but I got different results than comment 0: * IE and Edge display it correctly; `console.log(document.characterSet);` reports Windows-1252 as expected. * Firefox uses Windows-1258 encoding, according to the Page Info window. * Vivaldi mangles it in a different way; `console.log(document.characterSet);` reports Windows-874. > which used to work until one of the latest updates. Can you find the exact regression range? If not, do you remember the most recent version that definitely worked? https://mozilla.github.io/mozregression/quickstart.html
Bug 1615836 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to ersatzemail from comment #2) > It was actually a local file; Could you please [attach the file](https://bugzilla.mozilla.org/attachment.cgi?bugid=1615836&action=enter)? Feel free to edit it beforehand, as long as there's enough content left to reproduce the problem. > in fact it occurs in many similar files I used Notepad to save the attached testcase as ANSI, but I got different results than comment 0: * IE and Edge display it correctly; `console.log(document.characterSet);` reports Windows-1252 as expected. * Firefox uses Windows-1258 encoding, according to the Page Info window. * Vivaldi mangles it in a different way; `console.log(document.characterSet);` reports Windows-874. > which used to work until one of the latest updates. Can you find the exact regression range? If not, do you remember the most recent version that definitely worked? https://mozilla.github.io/mozregression/quickstart.html **Edit:** You may have had a text encoding for legacy content set. As I mentioned at comment 1, that was removed in bug 1551276 (Firefox 73).