mirror of
https://github.com/gorhill/uBlock.git
synced 2026-03-11 09:04:36 +00:00
Updated Quick guide: popup user interface (markdown)
parent
ec91a93ea6
commit
a241ce4df4
1 changed files with 1 additions and 1 deletions
|
|
@ -106,7 +106,7 @@ So if you were to create a filter such as `||example.com^`, and then navigate to
|
|||
|
||||
uBlock respected that semantic until version 0.9.3.0. With version 0.9.3.0, uBlock will subject web pages themselves to filtering. This means that using the same test case above, **uBlock will block the web page** served by <https://example.com> (unlike Adblock Plus):
|
||||
|
||||

|
||||

|
||||
|
||||
Why the change? Because [issue #1013](https://github.com/chrisaljoudi/uBlock/issues/1013) brought forth why it is desirable sometimes to completely block a web site, as opposed to what the ABP-filtering semantic dictates.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue