Andrey Meshkov
Andrey Meshkov
I actually don't think there's any option to do that at the moment.
To be precise the bug is Apple's :( Since v2.8 we implemented a workaround that should've mitigated it, but there's still a small possibility of that happening.
@sfionov please triage, how important is this one?
@zloyden That's a CoreLibs issue
Currently, we allow all scriptlets in trusted lists only. As a part of this task consider allowing scriptlets (but not trusted ones) in all lists.
Works as expected, there is no way for us to know if the user accepted the certificate or not in the browser
Agreed. but I think we can implement this entirely in the page context without involving CoreLibs.
@zloyden Could it be due to the service worker caching?
Well, the problem is that it looks like a strange Firefox bug, these `AdGuard.BrowserExtensionHost.exe` processes are spawned by Firefox. More on native messaging just in case: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_messaging Anyways, let's analyze...
Huh, then we should escalate this