Extension disabled by Chrome today because suspected malware. Version 7.2.6

[jeffmcnabb]

Please complete the following information when submitting a feature request or bug report.

• Extension version: 7.2.6
• Browser name & version: Chrome for Mac 114.0.5735.198
• Operating system & version: MacOS 13.4

Today the Extension was disabled by my browser stating presumed malware. There is a massive list of errors, most of them looking like a facebook URL, I'll paste them best I can.

Refused to load the script 'https://static.xx.fbcdn.net/rsrc.php/v3i08b4/yN/l/makehaste_jhash/oB-1zj5xoC1uKNX_Lrp1R3AwY65gLP7c1YqT2pJyjJyx4nc8BgwtUWFGiSBofYwxDL9zf7tVOIoEZjdDuVI5ppn-8yw2-7muZ8bBeJLJLIWLHSWZ_5R5VvUiuFaCel7WBfOz9GLjdzcmC-05PyqgFyQ52rngICxCECxOkIxRiDas0fqBRvqcc9rHoMiMJ16P8yWKg0bs30JXM-GNbbTrl4zwrb195cUa0FUJCda.js?_nc_x=2lGi_xgVEQq' because it violates the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

Refused to load the script 'https://static.xx.fbcdn.net/rsrc.php/v3iRFa4/yQ/l/makehaste_jhash/J41h6kySuh_IlKP6hkFjAwuubxVIbihDG9FZhWJ99JK-hAT1iNAgfUK6mm-6ZN66kAwN67jyjUdfZf7N2uMkX4XsfYFOjISr6XLREoUOJgtqaajAwO-6pGOuP7weh7vVKDEk4ctgNwazqc3HlgjO1AT9n8uSsqN3fmaDjcKe-duvWVmaxkkbONYNeOdglT3JUXGHrmvz3k649c0pkMVlXUTWQyTQqBkx5Vvi7pRGQnLaOpxnW-lDHNLynwB8OtrU6tOex7IGqGRWr5zm_do9jLbbcIYWoamcPcc08AcApOC19_q5nrG1p55HfXW__mMnMkHkfZeeYB.js?_nc_x=2lGi_xgVEQq' because it violates the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

Any insight on this? Is actually a problem, or should I just override it and use the extension as is?

[wirwolf]

Have some problem. Google Store disabled the app in my Chrome and removed from the market

[jeffmcnabb]

I'm curious @wirwol - If you re-enable TGS 7.2.6 in your Chrome are you able to save a current session?
I was already planning to switch to the TGS-notrack form on GitHub, however my 7.2.6 version of this extension in Chrome will NOT let me save my session/make a backup so that I can import my windows into the new forked extension.
If you re-enable TGS 7.2.6 in your Chrome are you able to save a current session?
It truly may just be an issue where I have TOO many tabs/windows open that it broke the Session manager. Mine is completely blank, underneath "current session" and also underneath "recent sessions".
I can see my past saved sessions (which are old), and oddly there is an autosave session for 7.2.5 update and 7.2.4 update, however it did not create an autosave of 7.2.6 update... I'm considering trying to roll back to 7.2.5 and see if it lets me save my session at least.

[Alamingazipur]

Please complete the following information when submitting a feature request or bug report.

• Extension version: 7.2.6
• Browser name & version: Chrome for Mac 114.0.5735.198
• Operating system & version: MacOS 13.4

Today the Extension was disabled by my browser stating presumed malware. There is a massive list of errors, most of them looking like a facebook URL, I'll paste them best I can.

Refused to load the script 'https://static.xx.fbcdn.net/rsrc.php/v3i08b4/yN/l/makehaste_jhash/oB-1zj5xoC1uKNX_Lrp1R3AwY65gLP7c1YqT2pJyjJyx4nc8BgwtUWFGiSBofYwxDL9zf7tVOIoEZjdDuVI5ppn-8yw2-7muZ8bBeJLJLIWLHSWZ_5R5VvUiuFaCel7WBfOz9GLjdzcmC-05PyqgFyQ52rngICxCECxOkIxRiDas0fqBRvqcc9rHoMiMJ16P8yWKg0bs30JXM-GNbbTrl4zwrb195cUa0FUJCda.js?_nc_x=2lGi_xgVEQq' because it violates the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

Refused to load the script 'https://static.xx.fbcdn.net/rsrc.php/v3iRFa4/yQ/l/makehaste_jhash/J41h6kySuh_IlKP6hkFjAwuubxVIbihDG9FZhWJ99JK-hAT1iNAgfUK6mm-6ZN66kAwN67jyjUdfZf7N2uMkX4XsfYFOjISr6XLREoUOJgtqaajAwO-6pGOuP7weh7vVKDEk4ctgNwazqc3HlgjO1AT9n8uSsqN3fmaDjcKe-duvWVmaxkkbONYNeOdglT3JUXGHrmvz3k649c0pkMVlXUTWQyTQqBkx5Vvi7pRGQnLaOpxnW-lDHNLynwB8OtrU6tOex7IGqGRWr5zm_do9jLbbcIYWoamcPcc08AcApOC19_q5nrG1p55HfXW__mMnMkHkfZeeYB.js?_nc_x=2lGi_xgVEQq' because it violates the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

Any insight on this? Is actually a problem, or should I just override it and use the extension as is?

[Alamingazipur]

Please complete the following information when submitting a feature request or bug report.

• Extension version: 7.2.6
• Browser name & version: Chrome for Mac 114.0.5735.198
• Operating system & version: MacOS 13.4

Today the Extension was disabled by my browser stating presumed malware. There is a massive list of errors, most of them looking like a facebook URL, I'll paste them best I can.

Refused to load the script 'https://static.xx.fbcdn.net/rsrc.php/v3i08b4/yN/l/makehaste_jhash/oB-1zj5xoC1uKNX_Lrp1R3AwY65gLP7c1YqT2pJyjJyx4nc8BgwtUWFGiSBofYwxDL9zf7tVOIoEZjdDuVI5ppn-8yw2-7muZ8bBeJLJLIWLHSWZ_5R5VvUiuFaCel7WBfOz9GLjdzcmC-05PyqgFyQ52rngICxCECxOkIxRiDas0fqBRvqcc9rHoMiMJ16P8yWKg0bs30JXM-GNbbTrl4zwrb195cUa0FUJCda.js?_nc_x=2lGi_xgVEQq' because it violates the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

Refused to load the script 'https://static.xx.fbcdn.net/rsrc.php/v3iRFa4/yQ/l/makehaste_jhash/J41h6kySuh_IlKP6hkFjAwuubxVIbihDG9FZhWJ99JK-hAT1iNAgfUK6mm-6ZN66kAwN67jyjUdfZf7N2uMkX4XsfYFOjISr6XLREoUOJgtqaajAwO-6pGOuP7weh7vVKDEk4ctgNwazqc3HlgjO1AT9n8uSsqN3fmaDjcKe-duvWVmaxkkbONYNeOdglT3JUXGHrmvz3k649c0pkMVlXUTWQyTQqBkx5Vvi7pRGQnLaOpxnW-lDHNLynwB8OtrU6tOex7IGqGRWr5zm_do9jLbbcIYWoamcPcc08AcApOC19_q5nrG1p55HfXW__mMnMkHkfZeeYB.js?_nc_x=2lGi_xgVEQq' because it violates the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

Any insight on this? Is actually a problem, or should I just override it and use the extension as is?

[ossilator]

see #1263