prehistoric-systems/uBlock
1
0
Fork 0
mirror of https://github.com/gorhill/uBlock.git synced 2026-03-11 09:04:36 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Created What µBlock can and can not (currently) do (markdown)

Raymond Hill 2014-06-29 14:37:01 -07:00
parent 1b40e1d7f7
commit e2fd0d34da
1 changed files with 28 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
What-µBlock-can-and-can-not-(currently)-do.md Normal file

@ -0,0 +1,28 @@
#### "µBlock does not support element hiding".
Yes it does. Try entering `twitter.com##body` in the _"Your filters"_ text area
and visit twitter.com: the page will be blank.
What it doesn't support [yet](https://github.com/gorhill/uBlock/issues/4),
is the UI counterpart to "element hiding", i.e. being able to click on an element
to extract filters out of it.
#### "The memory usage isn't actually ABP's fault, _EasyList_ is like 40,000+ lines of rules that all have to be parsed by ABP".
µBlock also parse _EasyList_, _EasyPrivacy_, _Malware domains_ lists,
and _Peter Lowes's Ad server_ list out of the box and yet uses less than half the
memory of ABP.
#### "µBlock has all the features ABP has!"
No it doesn't. There are things ABP can do which µBlock can't at this time. I will
consider all feature requests, but I will implement only those which do not jeopardize µBlock's
defining traits: lean, efficient and minimalist.
Filters with the `$popup` option are ignored. At time of writing, I see 558 such
filters in _EasyList_. Chromium comes with a built-in popup blocker, which can be enabled
in the settings.
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 site.