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
Press the Back button => the page is unblocked (BUG), and if you open same video in other tab it won't be blocked.
Workaround: enable the option Immediately block pages on these sites once blocking conditions are met, which is . However now the blocking happens when you just type ro in google search, because the suggestions usually contain roblox.
Extension version 1.6
Browser: Supermium 119.0.6045.192 64-bit (should also happen in any modern Chromium-based browser, I use this browser because the extension doesn't work in the last supported version of Chromium - see #338)
OS: Windows 8.1 64-bit
The text was updated successfully, but these errors were encountered:
Oops, the initial issue belongs to https://github.com/proginosko/LeechBlockNG-chrome (I had wrong impression that the code was the same for all extensions %).
I can't verify whether the same issue is applicable for the Firefox extension, because it doesn't block by keywords at youtube at all (Firefox 119.0 32-bit / Windows 10 21H1 64-bit / extension's version 1.6).
I checked the behavior in other environment (Firefox 117.0.1 64-bit / Windows 21H1 64-bit / extension version 1.6), and blocking by keywords seems to work on YouTube, though the Back button cancels the blocking, so the original issue report is applicable to Firefox extension as well.
With default settings the rules to block pages by keyword are usually ignored when the Back button is pressed on the blocked page.
Scenario:
~roblox
, don't forget about the first entry, which is*
) +All Day
.Workaround: enable the option
Immediately block pages on these sites once blocking conditions are met
, which is . However now the blocking happens when you just typero
in google search, because the suggestions usually containroblox
.Extension version 1.6
Browser: Supermium 119.0.6045.192 64-bit (should also happen in any modern Chromium-based browser, I use this browser because the extension doesn't work in the last supported version of Chromium - see #338)
OS: Windows 8.1 64-bit
The text was updated successfully, but these errors were encountered: