Comment

Comment by mziulu

The add-on shouldn't block anything on its own, so if there's a problem it's probably on some filter list that the user enabled. There's a pretty good way to debug these situations though, the network request log ( https://github.com/gorhill/uBlock/wiki/The-logger ). It will let you see the history of requests for a given page, and one of the colums in the log lets you fine tune what uBlock should do for that particular request - so, if you see that something that you don't want to be blocked is filtered out, you can reverse that and reload the page.

EDIT: in the latest release (0.9.9.0 at the time of this writing) the request log will also tell you which list provides the rule that blocks a particular request, it's pretty handy to debug this kind of issue.

parent mziulu 11 years ago

No comments yet

Be the first to share your thoughts.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton