Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

General filter chit-chat #7

Closed
THEtomaso opened this issue Jul 16, 2018 · 2,468 comments
Closed

General filter chit-chat #7

THEtomaso opened this issue Jul 16, 2018 · 2,468 comments

Comments

@THEtomaso
Copy link

@THEtomaso THEtomaso commented Jul 16, 2018

This thread is a megathread about adblock discussions in general. Here one can request syntax help, reproduction confirmations, info about differences between adblockers, assistance with making new lists, and so on. They'll be answered or considered by the biggest Adfilt contributors, and occasionally by members of the uBlock Origin development team (although in an unofficial fashion). (This header section was last updated on the 24th of April 2019 by DandelionSprout.)

None of the rules for this thread are obligatorily enforced, but are considered customary as of at the time of the last edit:

  • Anything ad-, adblocker-, and adblocking-related of any sort goes.
  • Temporary derails are permitted.
  • Political discussions are only permitted if they are directly related to something adblock-related.
  • Disclosing personal opinions about everyday topics (e.g. family life, non-tech worklife, strong political stances, pizza toppings) is normally discouraged, on the assumption that it could lead to thread participants losing some of their respect for one another.
  • When mentioning websites that are (not) affected by adblocking, it is customary to wrap website names and adblocker entries into ` (Grave accents). This will allegedly make it harder for the websites to find this thread in search engines.
  • Swearing is normally permitted, but is considered bad form. Swearing as a part of an insultment is even more of a bad form.
  • While the following has not been a problem in this thread, they have been sporadic problems among uBO enthusiasts: It is advised to not be hyper-excited when writing comments, whereas reporting thread participants or this repo to GitHub (unless you have a very good reason) is probable grounds for insta-removal from the thread and for the humiliation and pariah-ism of you from the uBlock Origin community.
  • If you wish to emote-react to your own comment: Why not use Windows+. to insert the emote into the end of the actual comment instead? It'll save some vertical space as well. (This rule is sleeping for W7 users until 14th of January 2020, and for W8 users until further notice.)

This thread originally started out as a simple report about removing the blurring from the preview of a premium news article, and is still visible below this line:

———————————————————————————————————

Affected site:

https://www.aftenposten.no/

Example:

https://www.aftenposten.no/karriere/Viktoria-16-betaler-n-million-for-en-karrire-som-ender-nar-hun-er-40-12051b.html

Issue:

Cosmetic filtering blocks the "salesposter" for subscription articles.
This results in strangely abrupted page layouts, that gives you the impression that the pages haven't loaded properly, or has some type of error on them.
As annoying as these type of "salesposters" may look, it's better not to block them, to avoid confusion!

Problem filter:

Dandelion Sprouts norske filtre for ryddigere nettsider

Problem rule:

aftenposten.no##.widgets.widget-salesposter

--

  • OS/version: Windows 8.1 Pro (x64)
  • Browser/version: Pale Moon v27.9.3 (x64)
  • Adblock Extension/version: uBlock Origin v1.16.4.2 (XUL)
@DandelionSprout

This comment has been minimized.

Copy link
Owner

@DandelionSprout DandelionSprout commented Jul 16, 2018

At least originally, I felt it was a problem that the sales poster also blurred out the lower lines of the articles previews, and that it would therefore be better for people who didn't intend to subscribe, to remove the blur (which it appears to me that I can't do without also blocking the sales poster).

However, this is a perfectly good issue report and feedback, so I'll look into resolving this issue within the next 15min.

DandelionSprout added a commit that referenced this issue Jul 16, 2018
#7 made a splendid point about avoiding confusion, so I'll of course adhere to it.
@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Jul 16, 2018

I felt it was a problem that the sales poster also blurred out the lower lines of the articles previews

I think it only blures out the last line partially.
The line is still readable too, so it's not an issue.

Thanks for the quick fix! :)

@DandelionSprout

This comment has been minimized.

Copy link
Owner

@DandelionSprout DandelionSprout commented Jul 16, 2018

For me it seemed to give a slight blur to the last two lines, but that's just pedantics of mine. 😄

Closing the issue now that it has been fixed.

@DandelionSprout

This comment has been minimized.

Copy link
Owner

@DandelionSprout DandelionSprout commented Jul 16, 2018

Update:

After an hour of trial and error, I eventually uncovered that the line blur stemmed from aftenposten.no##.widgets-salesposter:before, with :before being some kind of pre-emptive pseudo-child-element that I've had very little prior experiences with.

Having now accomplished this win-win situation, I'll add the new and vastly improved entry to the list sometime today.
image

DandelionSprout added a commit that referenced this issue Jul 16, 2018
I found the true source of the line blurring of Aftenposten's paid article previews, thus hopefully solving #7 even better than before.

I also removed one Viaplay filter, because its usefulness had been far surpassed by my new 'Anti-IMDB List'.
@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Jul 16, 2018

aftenposten.no##.widgets-salesposter:before

Nice catch! :)

@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Aug 1, 2018

Same thing @ digi.no

Example:
https://www.digi.no/artikler/442745/

Fix:
digi.no##.faded-article-content:after

@DandelionSprout

This comment has been minimized.

Copy link
Owner

@DandelionSprout DandelionSprout commented Aug 1, 2018

Splendidly done of you to have researched it enough to have created a fix entry for it. This'll of course be added to the filter list as soon as possible. 💜

DandelionSprout added a commit that referenced this issue Aug 1, 2018
As per #7
@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Aug 1, 2018

Those type of pseudo-element syntaxes works just fine with uBO.
..but after a recent discussion in the Pale Moon forum, I discovered that ABP-based blockers seems to use a different method (see post 7):
https://forum.palemoon.org/viewtopic.php?f=46&t=19682/
Perhaps you're able to make sense of it?

@DandelionSprout

This comment has been minimized.

Copy link
Owner

@DandelionSprout DandelionSprout commented Aug 1, 2018

It doesn't seem to be possible to do it in Adblock Plus at all, from what I can determine.

Adblock Plus' syntax is quite the mess, since I suspect that they're using their goal of encouraging better ads, as a bad excuse to refuse to support new features that originate from other adblockers (e.g. URL wildcards á la google.* in element blocking rules, :has-text, etc.). Coupled with poor documentation (to the point where uBlock Origin GitHub issue threads are more informative about ABP features than ABP's official websites), few examples of such ABP-formatted entries in active use, and that I frankly don't even want to test my lists in Adblock Plus due to its simplified UI, indicates that I think that Adblock Plus is outdated and that I can't recommend its everyday usage in all but the most narrow of cases.

@DandelionSprout

This comment has been minimized.

Copy link
Owner

@DandelionSprout DandelionSprout commented Aug 1, 2018

There is the small theorethical possibility that it's possible to trick :-abp-properties into only detecting :before and :after elements, but I wouldn't place my bets on it. Plus that :-abp-properties isn't even supported in uBO or Nano due to performance concerns (Okay, so advanced adblockers aren't 100% universally covering, either, I must admit), so I can't use Nano's element picker to experiment with it.

@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Aug 1, 2018

Thanks for elaborating.

@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Aug 3, 2018

Fix for dagbladet.no:
dagbladet.no##.CTA-body-faded

Example:
https://www.dagbladet.no/tema/69884034/

DandelionSprout added a commit that referenced this issue Aug 3, 2018
As per #7.
@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Aug 3, 2018

Fix for tu.no:
tu.no##.faded-article-content:after

Example:
https://www.tu.no/artikler/440961/

DandelionSprout added a commit that referenced this issue Aug 3, 2018
As per #7.
@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Aug 4, 2018

OFF TOPIC:

Are you located in Norway?
I ask because I'm currently trying to solve a strange filter issue, but no one is able to reproduce it.
I've pretty much ruled out UA sniffing and other potentially browser-discriminating schemes at this point, so the most likely explanation seems to be that the problem is location-dependent.

So far, the respective filter authors have refused to include the necessary exceptions in their filters, on the count of them not being able to reproduce the issue from their ends.
If this situation remains, the best solution would probably be to include the exceptions in your filter, which is currently the best known Norwegian filter available.

Let me know if you're interested, and I'll post the links to the GitHub discussions here.

@DandelionSprout

This comment has been minimized.

Copy link
Owner

@DandelionSprout DandelionSprout commented Aug 4, 2018

Indeed I am a Norwegian who lives in Norway, and who'd be up for such a challenge.

@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Aug 4, 2018

Great!

Here are the two reference links:
ryanbr/fanboy-adblock#512
AdguardTeam/AdguardFilters#20596

It's a bit to read up on. :)

@DandelionSprout

This comment has been minimized.

Copy link
Owner

@DandelionSprout DandelionSprout commented Aug 4, 2018

I think I could be seeing the cause of the problem. Are you currently using I Don't Care About Cookies (or anything similar) as one of your filter lists?

@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Aug 4, 2018

No, as you can see from my tests, I made sure to troubleshoot it using ONLY the filters in question!

@DandelionSprout

This comment has been minimized.

Copy link
Owner

@DandelionSprout DandelionSprout commented Aug 4, 2018

Ah, okay.

I can confirm that popsugar.*#@##_evidon_banner works splendidly on my end, but this creates for an interesting situation that I need a few minutes to think on. Don't get too heated up in the meantime, I'm working on it.

@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Aug 4, 2018

So, you can confirm that you get a cookie consent warning that looks like this:

filterissue-popsugar3

And that any one of these three blocking rules alone is enough to block it?:

##.evidon-banner
###_evidon_banner
/evidon-banner.
@DandelionSprout

This comment has been minimized.

Copy link
Owner

@DandelionSprout DandelionSprout commented Aug 4, 2018

Yes, I can confirm that I get a cookie consent that looks like that, and that the latter two entries (except ##.evidon-banner) blocks it.

The thing I'm currently pondering on, is whether it'd be correct conduct or not of me to use my Norwegian list to cover up for the mistakes of mostly unrelated annoyances lists. I need some consideration time on it, and in the meantime there's nothing that stops you from placing popsugar.*#@##_evidon_banner into your personal entries in uBO, so that it's at least fixed on your end.

@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Aug 4, 2018

Yes, I can confirm that I get a cookie consent that looks like that, and that the latter two entries (except ##.evidon-banner) blocks it.

Are you absolutely sure that you tested this properly, and that this rule isn't whitelisted somewhere in your filters?
Because from my end, ##.evidon-banner completely blocks it!
(Whitelisted cosmetic rules aren't visible in uBO's logger, you know)

The thing I'm currently pondering on, is whether it'd be correct conduct or not of me to use my Norwegian list to cover up for the mistakes of mostly unrelated annoyances lists.

No worries.
Given this new "evidence", I think we'll be able to convice the other filter authors to include the necessary exceptions in their own filters.

in the meantime there's nothing that stops you from placing popsugar.*#@##_evidon_banner into your personal entries in uBO, so that it's at least fixed on your end.

Of course, I've already done that.
But my goal is to prevent others from running into the same problem. :)

@DandelionSprout

This comment has been minimized.

Copy link
Owner

@DandelionSprout DandelionSprout commented Aug 4, 2018

Are you absolutely sure that you tested this properly, and that this rule isn't whitelisted somewhere in your filters?

Okay, my fault, I tested it again with ##.evidon-banner and it blocks it.

I don't think this is a Norway-only problem: Because GDPR is involved in this, I'm thinking that Popsugar may have chosen (poorly) to differ between EU and non-EU visitors, but I'm trying to look for more proof of that they've done that. I've asked my friends about what they're seeing, one lives in an EU country, and one lives in a non-EU-nor-EEC Eastern European country, and I'm awaiting their replies.

@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Aug 4, 2018

Great, the issue have been confirmed then!!
I'll look into convincing the respective filter authors now.. :)

@gorhill

This comment has been minimized.

Copy link

@gorhill gorhill commented Feb 11, 2020

IDK what the change is, maybe it checks whether there is the property?

The scriptlet was bailing out if it detected that the target property had already been trapped. Now it no longer bails out -- worse case is an exception is thrown if it tries to trap a property which is not configurable but this is not an issue since all scriplets are executed inside a try-catch statement.

@Yuki2718

This comment has been minimized.

Copy link

@Yuki2718 Yuki2718 commented Feb 12, 2020

IDK what the change is, maybe it checks whether there is the property?

The scriptlet was bailing out if it detected that the target property had already been trapped. Now it no longer bails out -- worse case is an exception is thrown if it tries to trap a property which is not configurable but this is not an issue since all scriplets are executed inside a try-catch statement.

Ty for taking your time to explain it! I'm not sure if I got what you mean, but guess essentially now the scriptlet can 'wait' even after it already blocked the inline script.

@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Feb 13, 2020

@okiehsch:

Here's another page error fix for uBlock filters - Legacy:
https://forum.palemoon.org/viewtopic.php?f=29&t=23784/#p183654
(Moonchild explains the problem in the post above)

The OP seems to have left the building, but I tested the fix myself, and it works just fine!

@okiehsch

This comment has been minimized.

Copy link

@okiehsch okiehsch commented Feb 14, 2020

DandelionSprout added a commit that referenced this issue Feb 14, 2020
Probably worth mentioning in #7
@DandelionSprout

This comment has been minimized.

Copy link
Owner

@DandelionSprout DandelionSprout commented Feb 15, 2020

After seeing the Finnish list give a part-time contributor (peace2000) full-time push rights; and seeing Fanboy bolstering his empire with his very recently created anti-push-notifications list; I've wondered once again if it'd be possible to make Adfilt slightly less of a one-man show, and slightly more of an empire. And no, it's not an attempt at an after-death testimony this time around, but rather just to alleviate me of around 10-25% of my daily adblocking workload, while making some of my lists with the most potential even better and making them potential candidates for inclusion in adblockers (especially once/if uBO's list addition freeze ever thaws up again).

@THEtomaso:

  • Nordic List: Carte blanché for entries that target Norwegian and Danish far-right websites (i.e. those listed on Remover for Mainstream Tabloid and Alt-Right Sites); critical unbreakage for [Pale Moon / Seamonkey / similar platforms]; time-critical EasyPrivacy unbreakage.
  • Anti-Malware List: Creating whitelistings for individual sites for the already existing TLD blocking entries. For domains already whitelisted in his private list, it'll be his mandatory responsibility to visit them again (or check them for redirections or malware otherwise) to see if they still exist as actual sites.
  • The right to create and non-exclusively maintain one new blacklist file for URL shorteners, based on those in his private list, should he wish to do so.

@lassekongo83:

  • Staying On The Phone Browser: Officially having that list combining with and absorbing his own I Don't Want Your App list, and making him the official co-maintainer of Staying On The Phone Browser with near-'carte blanché' permissions. Note that :-abp-has and :-abp-contains is to be used; as is the use of #?# in entries with :style or ##+js, after I discovered it was possible to not ultra-break ABP by doing that; and that making hiding rules generic is great if it's reasonable to assume they'd always be related to app downloads.
  • Nordic List: The right to add, remove and/or modify entries for Viafree, Gamereactor and Eurosport, contingent on the use of domain.* in hiding rules, and using the new set of uBO ##+js names.

For absolutely everything else, they'd have to ask me about it in this thread as usual.

Upon their acceptance of these fairly strict expectations and limitations they'd have, I'd make them so-called "Collaborators" of this repo with full push rights, as it seems to be completely impossible to only give push rights to individual files in a repo... 😬

Any questions?

@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Feb 15, 2020

I appreciate the trust, DS, but I feel like I'm already spending way too much time with this stuff, so I'm actually not interested in maintaining any official filter list.
Before long, I'd probably find myself blocking a bunch of crap that most people consider useful anyway.

Besides, those so-called "far-right websites", which you refer to, requires exremely few site-specific rules.
I don't think it would be too much hassle for you, if I suggest a couple of rules for them, over a years time.

Also, you know where to find my unofficial list, and you're welcome to grab whichever rules you want from it (no credits required/wanted)! :)

@DandelionSprout

This comment has been minimized.

Copy link
Owner

@DandelionSprout DandelionSprout commented Feb 15, 2020

Ah, okay. Thanks for the thorough explanation.

Before long, I'd probably find myself blocking a bunch of crap that most people consider useful anyway.

Now that you mention it, there was indeed some relatively unusual things in your personal list that made me feel I had to consider for some days before concluding if I should give you the offer, such as social account links, donation banners, and LGBT websites. Eventually I concluded you'd successfully be able to stick to any responsibility ranges you'd be given, but I accept your self-insight in a positive way. 🙂

I don't think it would be too much hassle for you, if I suggest a couple of rules for them, over a years time.

Ah, okay, so they're not actually something we'd/you'd need to keep an eye on frequently. Great to know.

Also, you know where to find my unofficial list, and you're welcome to grab whichever rules you want from it (no credits required/wanted)! :)

I was hoping to save 2 hours of much-delayed work tonight on adding more TLD domain whitelistings, but I'll take on that task, then.

@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Feb 15, 2020

Now that you mention it, there was indeed some relatively unusual things in your personal list

Well, you've got some pretty weird blocking rules of your own, you know.
The difference is that I don't separate my rules into different list, sorted by categories, but keep everyting together in one big mess instead! :)

@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Feb 15, 2020

For the record; to avoid any misconceptions, which might arise from reading DS's latest posts:
I'm not a racist, nor do I support any type of hate groups!

@DandelionSprout

This comment has been minimized.

Copy link
Owner

@DandelionSprout DandelionSprout commented Feb 15, 2020

Ah. I think I needed that clarification most of anyone here, actually... 😅

I was on Twitter in 2015-17, and since then I've been overly paranoid when it comes to whether someone seems to be racist/supremacist/similar or not. You have my apologies, as it currently stands.

DandelionSprout added a commit that referenced this issue Feb 15, 2020
As per #7 (comment)
DandelionSprout added a commit that referenced this issue Feb 15, 2020
As per #7 (comment).
@krystian3w

This comment has been minimized.

Copy link
Contributor

@krystian3w krystian3w commented Feb 15, 2020

@DandelionSprout

This comment has been minimized.

Copy link
Owner

@DandelionSprout DandelionSprout commented Feb 15, 2020

At first glance the Beta version seems considerably better than the regular version, at least when looking into past activity and not just unread notifications.

@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Feb 18, 2020

I've been removing some annoyances from the nasty new interface @ deviantart.com today.
Got most of it covered now, but there's a few remaining elements, which I'd like to get rid of:

  • The "scroll to top" button.
  • The "comments" and "likes" counters on thumbnails (at the front page).

Any suggestions?

@krystian3w

This comment has been minimized.

Copy link
Contributor

@krystian3w krystian3w commented Feb 18, 2020

Without log on?


Arrow with "JS":

deviantart.com#?##root > div:-abp-has(> span > svg[viewBox])
@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Feb 18, 2020

No, that leaves an empty container.

@krystian3w

This comment has been minimized.

Copy link
Contributor

@krystian3w krystian3w commented Feb 18, 2020

OK.


likes and comments maybe:

deviantart.com#?#div:-abp-has(> div:-abp-has(> span) + a[aria-label="Comment"])
deviantart.com#?#div:-abp-has(> div:-abp-has(> span) + button[aria-label="Favourite"])
@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Feb 18, 2020

No, I'm afraid not.
I've removed those things from everywhere else, except for the ones on thumbnails (only the counters themselves remain)!

@krystian3w

This comment has been minimized.

Copy link
Contributor

@krystian3w krystian3w commented Feb 18, 2020

So you try remove only numbers and not touch icons and other sections?

##path[transform="rotate(-180 12 12.5)"]:nth-ancestor(4)

##path[transform="rotate(-180 12 12.5)"]:xpath(../../../..[span])

maybe also cut arrow property and safe!


or slow:

###root > div:last-child:last-of-type:matches-css(position: fixed):matches-css(bottom: 16px):matches-css(right: 16px)
@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Feb 18, 2020

Yes, this took care of the "scroll to top" button!:
deviantart.com##path[transform="rotate(-180 12 12.5)"]:xpath(../../../..[span])
Good job, krystian3w!! 👍

This is what remains:

deviantart-counters

@krystian3w

This comment has been minimized.

Copy link
Contributor

@krystian3w krystian3w commented Feb 18, 2020

OK - so I must save any solution and refresh page to test problem with remains.

@krystian3w

This comment has been minimized.

Copy link
Contributor

@krystian3w krystian3w commented Feb 18, 2020

##:xpath(//span[contains(text(), 'Comments') or contains(text(), 'Favourites')]/../..[div][@class]/..[div][@class])

both, maybe no safe...


##:xpath(//span[contains(text(), 'Comments') or contains(text(), 'Favourites')]/..[@class])

only numbers into one filter

@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Feb 18, 2020

They both work!
Thanks a lot for this, krystian3w!
I wouldn't have been able to come up with those rules myself! :)

btw; what do you meen by "maybe no safe"?

@krystian3w

This comment has been minimized.

Copy link
Contributor

@krystian3w krystian3w commented Feb 18, 2020

I am going back 3 elements up from span, a bit much like lonely text.

--

Also I found this:

Note that // selects and searches over all nodes of the document which can be slow. Instead, if the structure of the document is known then use a proper path

So this filter can also take a long time to run or break the responsiveness of a website.

@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Feb 18, 2020

I just discovered that I can't use this rule:
deviantart.com##:xpath(//span[contains(text(), 'Comments') or contains(text(), 'Favourites')]/../..[div][@class]/..[div][@class])
..because it breaks the actual comment fields.

This rule seems to work just fine though!:
deviantart.com##:xpath(//span[contains(text(), 'Comments') or contains(text(), 'Favourites')]/..[@class])
:)

--

this filter can also take a long time to run or break the responsiveness of a website.

No worries..
AFAIC, DeviantArt has already managed to do that themselves!

@krystian3w

This comment has been minimized.

Copy link
Contributor

@krystian3w krystian3w commented Feb 18, 2020

Maybe @lassekongo83 generate pure CSS fast solutions.

@THEtomaso

This comment has been minimized.

Copy link
Author

@THEtomaso THEtomaso commented Feb 19, 2020

Full list of annoyance rules:

deviantart.com##:xpath(//span[contains(text(), 'Comments') or contains(text(), 'Favourites')]/..[@class])
deviantart.com##.navbar-menu-inner-scroll
deviantart.com##[aria-label^="Favourite"]
deviantart.com##[aria-label="Comment"]
deviantart.com##[aria-label="Share"]
deviantart.com##[data-hook^="comment_"]
deviantart.com##[data-hook="comments_counter"]
deviantart.com##[data-hook="fave_button"]
deviantart.com##[data-hook="faves_counter"]
deviantart.com##[data-hook="share_button"]
deviantart.com##[title="comments"]
deviantart.com##a[href*="#comments"]
deviantart.com##a[href*="facebook.com"]
deviantart.com##a[href*="instagram.com"]
deviantart.com##a[href*="twitter.com"]
deviantart.com##path[transform="rotate(-180 12 12.5)"]:xpath(../../../..[span])
deviantart.com##span:has-text( Today)
deviantart.com###outdated_banner
deviantart.com###overhead-promo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.