Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow a shield toggle to enable/disable cosmetic filtering
See original GitHub issueDescription
Having another shield option to allow us to disable/enable cosmetic filtering on a per site basis.
Was discussed here; https://github.com/brave/brave-browser/issues/8688
To be used to help debug webcompat issues (by us and by the user), an easy option to disable cosmetic filter to help where we need to. Cosmetic filter default should stay enabled by default.
Miscellaneous Information:
uBO has a similar filter option, https://github.com/gorhill/uBlock/wiki/Per-site-switches#no-cosmetic-filtering
If a cosmetic filtering shield option isn’t viable, making a custom option in chrome://settings/content/siteDetails might be a middle ground (just an idea).
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Closing this one out. Fixed with -> https://github.com/brave/brave-browser/issues/8475
@antonok-edm that initial decision (no shields toggle) was because, in the initial proposal, the original options were either “default on, with 1p vs 3p distinctions” (i.e. what we shipped) or “default off, with shields toggle”.
But now that we’re default on, I think a shields toggle would be fine with
options.