Limits on wildcards?

[IAmBroom]

Something simply isn't working with wildcards in custom filters. From what I've read, *popup* should block any url containing the phrase "popup", when in fact it never blocks anything.

Are wildcards not allowed at the beginning of URL filters?

[mapx]

provide an example page and explain what do you want to block

[IAmBroom]

Good point.

On http://learnbonds.com/ the filter overlay does not prevent the whole-screen translucent overlay
learnbonds.com##.optin-monster-overlay

The filter nudge does not block the following two bottom-screen popup elements from meetup.com:
meetup.com###group_home_nudge__desktop_group_jan_promo_nudge
meetup.com##.mt-fixToBottom.mt-alert.mt-nudge.paddingAll.inverted.mt-alert--visible

(I was not logged in to either site, BTW.)

EDIT: The meetup popup appears instantly, but has "Jan_promo" in its address, so it may not always pop up in the future. The LearnBonds popup takes several seconds to appear.

[mapx]

- the wildcards are working for blocking filters
- you are talking about hiding filters (for css elements in the page)

the filters you want are something like:
learnbonds.com##[class$="overlay"]
meetup.com##[id$="nudge"]

or (not specific on domains)
##[class$="overlay"]
##[id$="nudge"]

class$ ==> means the last part of that class is "overlay"
class* ==> could be any part in the class name
class^ ==> the first part of the class name

read more about hiding filters:
en/filters#elemhide_attributes

Anyway, if you are using firefox, install also EHH (element hiding helper) which works together ABP and help you creating hiding filters. Use it in advanced mode.
In chrome, click ABP icon, "block element", select the element in the page and again you can create blocking / hiding filters.

[IAmBroom]

Thank you! That's very clear.

[fanboy]

From the Annoyances list, which seems to remove the overlay nicely.

Code: Select all

##.optin-monster-overlay
/plugins/optin-monster/*$script