UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36

Example URL:
https://cdneu.wmbcdn.com/images/default2/default/jsCore/mambo/utils//Commet.js

Steps to reproduce the problem:
1. go to: https://cdneu.wmbcdn.com/images/default2/default/jsCore/mambo/utils//Commet.js

2. Look at line 13 (the first row in the comment-block) and notice that the text is not displayed correctly

What is the expected behavior?
The text should be displayed correctly.

What went wrong?
Chrome fail to auto detect the correct encoding for the page, and since there's no longer any manual way to tell chrome what encoding to use it is no longer possible to solve the display problem.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes Around here I would guess: https://bugs.chromium.org/p/chromium/issues/detail?id=597488

Does this work in other browsers? Yes

Chrome version: 69.0.3497.100  Channel: n/a
OS Version: 10.0
Flash Version: 

It's almost a bit arrogant to think it is possible to write some auto detect algorithm that will be able to handle all combinations of misconfigured web servers and creative content pages created by extremely ingenious and creative web developers.

K.I.S.S!

Do the auto detect, but make sure there's a manual override setting for cases when the auto detect doesn't work.

If the Autodetect had picked UTF-8 instead of 7-bit ASCII or whatever it picked, it would have worked.

IE also get's it wrong by default, but if you go to the View menu in IE and select UTF-8 it display just fine.