Constant 'Debugging' banners

[sprig]

Hi!

Thanks for making this extension. Recently upon installing in chromium 139 from the store I'm getting constant banners stating "NoScript started debugging this browser" when opening new tabs. It is a bit annoying because they often stay for several seconds, sometimes closing and sometimes lingering forever.

[vladimirRadjenovic]

Hmm, I am not a part of this project but you can hide this notification bar by launching Chrome with a --silent-debugger-extension-api flag.

How to run Chrome with flags

[gititgotitgoood]

Same issue here

[hackademix]

This is very likely because

1. You're on a Chromium-based browser
2. On those page you've got the script capability enabled and the webgl capability disabled.

Unfortunately the severe limitations of the WebExtensions API in general, and of Chrome's Manifest V3 in particular, makes using the debugging API (and therefore the browser spawning those ugly banners) the only hack possible on Chromium to inject extensions code in web workers and modify their JavaScript execution environment.

On Firefox we can use other hacks based on the blocking asynchronous 'webRequest` API, which Google has never fully implemented in Manifest V2 and has completely disabled in Manifest V3.

These hacks are necessary for effectively disabling capabilities which can be accessed not just from DOM windows but also from web workers, such as webgl via the OffscreenCanvas API.

I've been advocating for new Manifest V3 APIs to make these and other hacks less complicated and invasive, including a workers injection API which is endorsed also by Duck Duck Go developers, but they're still at the proposal stage.

Until Chromium devs decide to implement something like that, I'm afraid the best you can do is following @vladimirRadjenovic's suggestion above :(