-
-
Notifications
You must be signed in to change notification settings - Fork 191
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
Disable menu won't open #2453
Comments
also reloading the same page will show adnauseam enabled on it even while the page being whitelisted |
thank you @urfausto for the posting this. Indeed it was a bug, I am fixing it now and should be there in the next release quite soon: Regarding the behaviour of the menu, it is designed in the way where the disable popup window will only show if you re-enable the page and disable it again, maybe not the most intuitive. Let's see how we can improve it. |
thank you for the fix.
hmmm, forget about it. now i've noticed that going to a page where i know adn is disabled, adn will actually show it is disabled. |
one more thing about the extension's menu: even when i enable 'Strict Blocking Mode' it will randomly show as active or strict on different pages (per website)... can't get my head around it! so confusing!!! |
@urfausto can you give us steps on how to recreate this problem ? |
i really have no idea. it seems completely random!!! i have strict mode enabled in the options but on some websites it will show as active! i have some custom third parties filters added and these are my settings: also localcdn in my extensions. |
I tried to reproduce the issue when...
Description
hi, i'm on vivaldi 5.3, windows 7 x64, and when i disable adnauseam on a page i can't open the disable menu window anymore. clicking does nothing and this little frame will only open the first time you disable the extension on the given page. any feedback on this? thanks.
URL(s) where the issue occurs.
No response
Screenshot(s)
No response
Steps to Reproduce
No response
Configuration
first install
The text was updated successfully, but these errors were encountered: