Set Character Encoding

What is there in this extension that would not theoretically work in Chrome versions earlier than 125? (minimum_chrome_version: 125) We are not considering forks and popular Chrome modifications that do not have a manic chase for updates with increasing versions. Are we preventing them from installing this extension?

最新几个版本chrome无法使用 错误： Context menu updated 3bg.js:119 Uncaught (in promise) TypeError: Error in invocation of declarativeNetRequest.updateDynamicRules(declarativeNetRequest.UpdateRuleOptions options, optional function callback): Error at parameter 'options': Error at property 'addRules': Error at index 0: Error at property 'id': Invalid type: expected integer, found number. at onClickHandler (bg.js:119:44)

com pholodyDeveloperAug 8, 2024

Thanks for feedback. This isssue is fixed in Version 1.0.1. Please update and have another try.

Seems not to work as of June/July :( Thanks Google.

com pholodyDeveloperAug 8, 2024

Thanks for feedback. There was an issue in last version. Plese update to Version 1.0.1 and have another try. Please feel free to leave a message if it does not work.

not working

com pholodyDeveloperAug 8, 2024

Thanks for feedback. There was an issue in last version. Plese update to Version 1.0.1 and have another try. Please feel free to leave a message if it does not work.

chrome version 126.0.6478.57 or 125 the same When I open txt log file (://doman/log.txt) and set page encoding, it will become html mode so my newline (\n) become to one line, can it be fixed ? :(

not working

com pholodyDeveloperAug 8, 2024

Hi. Can you share the URL that did not work. We will investigate on it.

Great. Restores the function, removed by Google.

Good, just that some webside have locked the right-click function which prevent us from using this extension. hope there's an alternative way to change the encording.

Does what it says.

The extension results in the below error when accessing Oracle Cloud Console. Unexpected Error Something went wrong. Please try again later. Removing or disabling this extension fixed the issue. I noticed this behavior with one more extension : EditThisCookie Disabling both this Extension EditThisCookie Set Character Encoding fixes the issue. Observed this in Latest chrome version.