Dim the 'Ignore generic cosmetic filters' option when appropriate #1940
Comments
|
I can't make exceptions for user filters, one single generic cosmetic filter would cause all the expected benefits from using this setting to completely disappear -- it takes only one single generic cosmetic filter to exist for uBO to be forced to survey the DOM of a document. Since the re-factoring of 3rd-party pane, it is no longer displayed as a sub-option, so this is no longer an issue. |
|
I just had an idea how uBO could disabling DOM surveying while allowing user's own generic cosmetic filters: to simply just inject them all unconditionally. The worry though is that a user would paste a huge amount of generic filters in their My filters pane. Reopening, to assess more thoroughly this implementation idea. |
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Issue Report Synopsis:
When the Parse and enforce cosmetic filters option is disabled, the Ignore generic cosmetic filters sub-option is not dimmed.
Test Environment:
uBlock Origin version: 1.9.0
Firefox version: 48.0.2 (applies to 32-bit and 64-bit)
Steps To Reproduce:
Expected Behavior:
When Parse and enforce cosmetic filters is disabled (unchecked), the Ignore generic cosmetic filters option should be dimmed.
Recommendation:
Dim the Ignore generic cosmetic filters option when Parse and enforce cosmetic filters is disabled (unchecked).
The text was updated successfully, but these errors were encountered: