Implement support for :style cosmetic filters #86
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
remusao
force-pushed
the
cosmetic-style-filters
branch
from
389ce3e
to
3f6106c
Compare
zhonghao-cliqz
approved these changes
Jan 10, 2019
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Filters of the form
domains##selector:style(custom style)can be used to apply a custom style to elements of the DOM (instead of hiding). This is needed to defuse some anti-adblocking mechanisms.Changelog:
getCosmeticsFilterswill now return CSS as a single string(stylesheet) instead of a list of selectors. This simplifies the usage and
allows to directly inject this into the page using the method of your
choice: through content scripts or tabs.injectCSS API.