From a241ce4df4c59cb9a361d9fb931bfb99ece2e299 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Mon, 15 Jun 2015 08:40:45 -0400 Subject: [PATCH] Updated Quick guide: popup user interface (markdown) --- Quick-guide:-popup-user-interface.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Quick-guide:-popup-user-interface.md b/Quick-guide:-popup-user-interface.md index e1cbdd2..95983bb 100644 --- a/Quick-guide:-popup-user-interface.md +++ b/Quick-guide:-popup-user-interface.md @@ -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 (unlike Adblock Plus): -![Page was fully blocked](https://raw.githubusercontent.com/gorhill/uBlock/master/doc/img/page-block.png) +![Page was fully blocked](https://cloud.githubusercontent.com/assets/585534/8160013/14466ca0-133a-11e5-8d3c-28169288f35a.png) 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.