From ef9052d1ab8cc5dd5ad7fc79204bcb5267e9b923 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Sun, 14 Jun 2015 07:28:13 -0400 Subject: [PATCH] Updated Quick guide: popup user interface (markdown) --- Quick-guide:-popup-user-interface.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Quick-guide:-popup-user-interface.md b/Quick-guide:-popup-user-interface.md index f35b5d1..32fc4c8 100644 --- a/Quick-guide:-popup-user-interface.md +++ b/Quick-guide:-popup-user-interface.md @@ -151,4 +151,6 @@ Because of security and privacy concerns, many prefer to block all web fonts by no-remote-fonts: * true -This will block all web fonts everywhere by default, and in this case you can toggle off the switch to allow web fonts on a per-site basis. \ No newline at end of file +This will block all web fonts everywhere by default, and in this case you can toggle off the switch to allow web fonts on a per-site basis. + +**Caveat:** Chromium's webRequest API [does not specifically report requests of type `font`](https://developer.chrome.com/extensions/webRequest#type-ResourceType), fonts are reported as type `other`. Whether a request is for a font resource is inferred by uBlock using the "extension" of the path part of a URL. However a URL can be anything really, regardless of request type, so for Chromium-based browsers, uBlock **may** have to block a font **after** the request is made, when the response headers are received from the remote server -- as the response headers allow to identify for sure the type of a resource.