-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proceed button should not be allowed #3281
Comments
It is even easier for them to simply click the big power button and disable uBO entirely on a site. Or they can simply disable the uBO extension in the browser. Either of these would allow the user to easily access the URL. If you are trying to use uBO for parental control, then that is not what it is designed for. You would be better served by using another product that is specifically designed for this purpose. |
Possible duplicates: For multi-user setup, use system accounts. You can make uBO setup bit more strict by administrative policies https://github.com/uBlockOrigin/uBlock-issues/wiki/Deploying-uBlock-Origin:-configuration |
I do realise that your request is related to "My filters", but since your statement sounds very generic, my reply will be as much generic too: as far I remember, since the beginning, purpose of strict blocking was to serve as a warning message, not as a parental control:
Like already mentioned in the earlier comments, as far I remember, uBO doesn't serve as a parental control extension, there are many declined requests: |
Issue:
After user1 has added an URL to 'My Filters' those URLs are expected to be blocked in Firefox.
However, if another user (user2) comes along and tries that URL, a proceed button appears. This button is further highlighted in blue.
It is very easy for user2 to click on proceed and unblock that URL. The proceed button and the blue highlighting defeats the purpose of having a URL blocker and acts as a mere warning if the user cares to read about it.
Potential solution(s):
Potential Improvement(s)
The text was updated successfully, but these errors were encountered: