From 75a2ab96b415cc476c71d506609252e813f4fec6 Mon Sep 17 00:00:00 2001 From: gwarser Date: Fri, 23 Nov 2018 01:17:32 +0100 Subject: [PATCH] Mention text encoding in HTML filters --- Static-filter-syntax.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Static-filter-syntax.md b/Static-filter-syntax.md index 1fa8f4d..5a7c5bf 100644 --- a/Static-filter-syntax.md +++ b/Static-filter-syntax.md @@ -224,7 +224,7 @@ For example, [AdGuard English filter](https://kb.adguard.com/en/general/adguard- Supported by uBO 1.14.23b3+ in Firefox 57+. -**READ VERY CAREFULLY:** HTML filtering acts on the **response data** (before browser parsing). Do not use the browser inspector from developer tools to create HTML filters. You **must** use `view-source:[URL of page]` instead to look at the **response data** and find out relevant information to create relevant HTML filters. +**READ VERY CAREFULLY:** HTML filtering acts on the **response data** (before browser parsing). Do not use the browser inspector from developer tools to create HTML filters. You **must** use `view-source:[URL of page]` instead to look at the **response data** and find out relevant information to create relevant HTML filters. Only UTF-8 encoding is supported natively by browsers. For other (most used) encodings, custom encoders are implemented in JavaScript. Because of this, HTML filtering will work only on pages with character encoding compatible with: UTF-8, ISO-8859-1, Windows-1250, Windows-1251 and Windows-1252 ([detailed maping](https://github.com/gorhill/uBlock/blob/2a91a685ce3d2dae5d3c285cff1bc74a1982be74/src/js/text-encode.js#L32)) The purpose of HTML filters is to remove elements from a document _before_ it is parsed by the browser.