uBlock Origin : Cross-site cosmetic filtering?
up vote
1
down vote
favorite
Is there a way to block cosmetic elements on multiple sites. For example on StackExchange, I would like to block
##.site-footer--container
##.site-header
###left-sidebar
But, I don't want ot just block them on a subdomain of stackexchange, I would like to block them on all sites on stackexchange, for example
*.stackexchange.com
However, a rule like
*.stackexchange.com##.site-header
does not work, but a rule like
dba.stackexchange.com##.site-header
Will work, (though on just the dba.
subdomain)
google-chrome-extensions adblock
add a comment |
up vote
1
down vote
favorite
Is there a way to block cosmetic elements on multiple sites. For example on StackExchange, I would like to block
##.site-footer--container
##.site-header
###left-sidebar
But, I don't want ot just block them on a subdomain of stackexchange, I would like to block them on all sites on stackexchange, for example
*.stackexchange.com
However, a rule like
*.stackexchange.com##.site-header
does not work, but a rule like
dba.stackexchange.com##.site-header
Will work, (though on just the dba.
subdomain)
google-chrome-extensions adblock
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Is there a way to block cosmetic elements on multiple sites. For example on StackExchange, I would like to block
##.site-footer--container
##.site-header
###left-sidebar
But, I don't want ot just block them on a subdomain of stackexchange, I would like to block them on all sites on stackexchange, for example
*.stackexchange.com
However, a rule like
*.stackexchange.com##.site-header
does not work, but a rule like
dba.stackexchange.com##.site-header
Will work, (though on just the dba.
subdomain)
google-chrome-extensions adblock
Is there a way to block cosmetic elements on multiple sites. For example on StackExchange, I would like to block
##.site-footer--container
##.site-header
###left-sidebar
But, I don't want ot just block them on a subdomain of stackexchange, I would like to block them on all sites on stackexchange, for example
*.stackexchange.com
However, a rule like
*.stackexchange.com##.site-header
does not work, but a rule like
dba.stackexchange.com##.site-header
Will work, (though on just the dba.
subdomain)
google-chrome-extensions adblock
google-chrome-extensions adblock
asked Nov 24 at 2:02
Evan Carroll
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
Apparently, the regex patterns for uBlock are not anchored, so you can do
stackexchange.com###left-sidebar
stackexchange.com##.site-header
stackexchange.com##.site-footer--container
To trim down the bloated Stack Exchange sites.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
Apparently, the regex patterns for uBlock are not anchored, so you can do
stackexchange.com###left-sidebar
stackexchange.com##.site-header
stackexchange.com##.site-footer--container
To trim down the bloated Stack Exchange sites.
add a comment |
up vote
2
down vote
Apparently, the regex patterns for uBlock are not anchored, so you can do
stackexchange.com###left-sidebar
stackexchange.com##.site-header
stackexchange.com##.site-footer--container
To trim down the bloated Stack Exchange sites.
add a comment |
up vote
2
down vote
up vote
2
down vote
Apparently, the regex patterns for uBlock are not anchored, so you can do
stackexchange.com###left-sidebar
stackexchange.com##.site-header
stackexchange.com##.site-footer--container
To trim down the bloated Stack Exchange sites.
Apparently, the regex patterns for uBlock are not anchored, so you can do
stackexchange.com###left-sidebar
stackexchange.com##.site-header
stackexchange.com##.site-footer--container
To trim down the bloated Stack Exchange sites.
answered Nov 24 at 2:05
Evan Carroll
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377926%2fublock-origin-cross-site-cosmetic-filtering%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown