You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the browser suspends the Service Worker its reactivation takes an inordinately long time.
In this time frame, which in my opinion is about 10 sec, the filtering ability of the extension is non-existent.
It is possible to verify this by following this procedure:
Open only “edge (or name browser)://extensions/” so no other tabs open.
that you had previously saved in your favorites bar and wait without doing anything for the warning at the bottom indicated by the red arrow in the image to filter out.
This procedure also highlights the lack of filtering when the browser is first opened
Proposed solution
A shorter time for reactivation of suspended Service Worker from the browser
Alternative solution
I did the same test with uBLock Origin Lite.
The problem does not appear to be present.
The text was updated successfully, but these errors were encountered:
adguard-bot
changed the title
Request Service Worker reactivation in less time than the current time (10 sec?).
Improve Service Worker reactivation time
Nov 19, 2024
Issue Details
When the browser suspends the Service Worker its reactivation takes an inordinately long time.
In this time frame, which in my opinion is about 10 sec, the filtering ability of the extension is non-existent.
It is possible to verify this by following this procedure:
https://msfn.org/board/
that you had previously saved in your favorites bar and wait without doing anything for the warning at the bottom indicated by the red arrow in the image to filter out.
This procedure also highlights the lack of filtering when the browser is first opened
Proposed solution
A shorter time for reactivation of suspended Service Worker from the browser
Alternative solution
I did the same test with uBLock Origin Lite.
The problem does not appear to be present.
The text was updated successfully, but these errors were encountered: