-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Blocks addons that use the sidebar #184
Comments
I checked my Whitelist and "behind-the-scene" was already there, but the sidebar only loaded if I completely disabled uBlock. |
Somehow I missed that new issue. I will investigate. Version 0.9.7.0 will come with a unified logger, it will be easier to diagnose the problem, as selecting a tab to inspect will no longer be necessary. |
By the way, you don't provide much details, I don't even know which browser you are using. Also, a link to the add-on with which the issue can be reproduced -- one not requiring the creation of an account etc. is preferred. |
Apologies. I'm using multiple recent versions of Firefox on different computers. The extension is TickTick (https://addons.mozilla.org/en-US/firefox/addon/ticktick/?src=search). You should be able to see the problem without creating an account, but it will be more obvious if you sign in. |
Can you verify with the unified logger if now you can see (and act upon) whether network requests for the add-on are showing in the logger? |
Sorry for the delay. Yes, the requests do now show up in the logger. Thanks! On Sat, May 16, 2015 at 9:17 AM Raymond Hill notifications@github.com
|
I need to fix something in order for the popup to be filled properly when opened from the logger for the current scenario. Will fix asap. |
Brilliant, thanks! |
Some addons utilize a sidebar to display data. This data is subject to blocking by uBlock but there is no way to interact with this data in order to add rules, etc. One example is the TickTick addon (task manager). The only way to get this addon to work is to completely disable uBlock.
The text was updated successfully, but these errors were encountered: