There are two kinds of ABP-compatible filters: network filters and cosmetic filters. Cosmetic filters are referred to as element hiding filters by Adblock Plus (ABP).
Network filters
Short answer: resources blocked: network requests are cancelled before they leave the browser.
The purpose of network filter is to prevent a network request to be made to a remote server, so as to prevent downloading a remote resource. uBlock Origin (uBO) will prevent the network request from even being made. This saves bandwidth, decrease privacy exposure -- as the remote server won't be able to log anything if you do not contact it.
Hosts file
Short answer: resources blocked: network requests are cancelled before they leave the browser.
uBO 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.
Blocked network requests are nipped in the bud.
Cosmetic filters
Short answer: resources hidden -- in various ways depending on the class of cosmetic filters.
These filters serve to visually 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, uBO will hide DOM elements on a web page which match cosmetic filters. uBO uses a different method than other big-name blockers to hide the DOM elements though.
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: the slower the computer, the higher the likelihood
- Solution for when the behavior occurs and is an issue for a user: to create the appropriate specific cosmetic filter.
- Cached generic cosmetic filters: injected before page's root DOM is loaded
- No flickering
Also, a very simple test page to find out if cosmetic filtering can be bypassed in your blocker: http://raymondhill.net/ublock/adbox.html.
More details regarding network filtering
When a network request is filtered, both uBO and ABP will collapse the DOM counterpart -- if any -- of a blocked network request. They both work the same way in such scenario, in the absence of a cosmetic filter matching the DOM counterpart of a blocked network request.
In both uBO and ABP, this occurs after the DOM is loaded, so in both cases, users may be able to visually notice the placeholder collapsing after the page loads.
Yet, uBO is at an advantage in such case: since it does not inject thousands of CSS rules in a page (and frames within that page), this means it makes itself available sooner to handle the task of collapsing the DOM counterpart of blocked network requests. This can be clearly appreciated in the following test page:
- Chromium + uBO: minimal flickering (sometimes none)
- Chromium + ABP: noticeable flickering
- Firefox + uBO: no flickering
- Firefox + ABP: no flickering
Another advantage of uBO here is that these collapsed-DOM-counterpart-of-blocked-network-requests are cached as temporary specific cosmetic filters internally.