mirror of
https://github.com/gorhill/uBlock.git
synced 2026-03-11 09:04:36 +00:00
Updated Does µBlock blocks ads or just hide them? (markdown)
parent
9853309750
commit
16038d60d0
1 changed files with 15 additions and 6 deletions
|
|
@ -18,6 +18,12 @@ The purpose of network filter is to prevent a network request to be made to a re
|
|||
|
||||
**Short answer:** resources blocked: network requests are cancelled before they leave the browser.
|
||||
|
||||
#### Hosts file
|
||||
|
||||
µBlock also support the parsing and enforcing of hosts files -- something which ABP does not. All entries in a hosts file are parsed as network filters, i.e. no resource will be fetch from a remote server which appear in a hosts file, no connection will even be attempted.
|
||||
|
||||
**Short answer:** resources blocked: network requests are cancelled before they leave the browser.
|
||||
|
||||
#### Cosmetic filters
|
||||
|
||||
These filters serve to remove DOM elements from a web page. They have no value privacy-wise, it is essentially to make web page look better by removing unwanted content, which usually cannot be blocked using network filters. Just like ABP, µBlock will hide DOM elements on a web page which match cosmetic filters. µBlock uses a [different method](https://github.com/gorhill/uBlock/wiki/Cosmetic-filtering-in-%C2%B5Block:-version-0.4.0.0-update) than other big-name blockers to hide the DOM elements though.
|
||||
|
|
@ -25,14 +31,17 @@ These filters serve to remove DOM elements from a web page. They have no value p
|
|||
Different classes of cosmetic filters are applied differently:
|
||||
|
||||
- Specific cosmetic filters: injected before page's root DOM is loaded
|
||||
- No flickering
|
||||
- Generic cosmetic filters: injected after page's root DOM is loaded
|
||||
- These are cacheable
|
||||
- Since these cosmetic filters are applied after page load, DOM elements **may** be hidden after they are rendered
|
||||
- Notice the emphasized "may": generally, you won't see this; and sometimes you will notice **more** flickering with ABP (with same filter lists):
|
||||
- Demonstration: [test page](http://raymondhill.net/ublock/tiles1.html)
|
||||
- Chromium + uBlock: minimal flickering
|
||||
- Chromium + ABP: noticeable flickering
|
||||
- Firefox + uBlock: no flickering
|
||||
- Firefox + ABP: no flickering
|
||||
- Cached generic cosmetic filters: injected before page's root DOM is loaded
|
||||
- No flickering
|
||||
|
||||
**Short answer:** resources hidden -- in various ways depending on the class of cosmetic filters.
|
||||
|
||||
#### Hosts file
|
||||
|
||||
µBlock also support the parsing and enforcing of hosts files -- something which ABP does not. All entries in a hosts file are parsed as network filters, i.e. no resource will be fetch from a remote server which appear in a hosts file, no connection will even be attempted.
|
||||
|
||||
**Short answer:** resources blocked: network requests are cancelled before they leave the browser.
|
||||
|
|
|
|||
Loading…
Reference in a new issue