Replies: 3 comments 10 replies
-
Are you blocking by keywords? |
Beta Was this translation helpful? Give feedback.
1 reply
-
If you don't allow access to website data for those sites, LeechBlock can't inject its content script into the page, which will reduce the functionality. So that's probably the issue here. Is there a reason you don't want to grant that permission to those sites? |
Beta Was this translation helpful? Give feedback.
2 replies
-
Hey @proginosko I'm giving LeechBlock NG access to site data for all sites and I'm still facing this problem. |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I find that some blocked sites in already open tabs do not get blocked even after the block starts. I have already selected the "Immediately block pages on these sites..." option. It works on some blocked sites and doesn't on some others. On the sites where it does not work, if I click a link or refresh the page, then the block kicks in. This is true across Edge, Chrome and FireFox. I disabled "access to website data" permission on all but some sites and it appears those that do not have access to website data have this issue. If this is indeed the reason, is there a workaround or fix that would allow the "immediate block" to work as intended regardless of that permission?
Beta Was this translation helpful? Give feedback.
All reactions