From f8b67c1e8554fe45975fad8fba21c3838fb7a159 Mon Sep 17 00:00:00 2001 From: gorhill Date: Thu, 9 Oct 2014 08:00:06 -0700 Subject: [PATCH] =?UTF-8?q?Updated=20What=20=C2=B5Block=20can=20and=20can?= =?UTF-8?q?=20not=20(currently)=20do=20(markdown)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- What-µBlock-can-and-can-not-(currently)-do.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/What-µBlock-can-and-can-not-(currently)-do.md b/What-µBlock-can-and-can-not-(currently)-do.md index d6aeffe..e608609 100644 --- a/What-µBlock-can-and-can-not-(currently)-do.md +++ b/What-µBlock-can-and-can-not-(currently)-do.md @@ -11,8 +11,6 @@ memory of [Adblock Plus](https://adblockplus.org/) ("ABP"), which is itself much #### "µBlock has all the features ABP has!" -µBlock doesn't have a _"Block element"_ entry in the contextual menu (right-click). The element picker can be used though to pick whatever element you do not want to see. Nobody asked for a contextual menu entry yet, so I don't consider it a sought-after feature, hence I didn't spend time implementing it. - Regular expression-based filters are not supported. At time of writing I see three such filters in _EasyList_, and none in _EasyPrivacy_. So rather uncommon. I may support them if there is really a need, but only for those which will have the `domain` filter option set: otherwise it's just impossible to implement efficiently such filters, and µBlock won't encourage their use by supporting these. For all the instances I have seen, it is possible to translate them into more efficient non-regex-based filters. Filters with the `$elemhide` option are ignored. At time of writing, I see 50 such filters in _EasyList_. The purpose of these filters is to disable cosmetic filters on specific sites.