From c1dbd9d4db9fd6ce9a135b3c6db32d1254c2676a Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Mon, 8 May 2023 16:23:56 -0400 Subject: [PATCH] Updated Per site switches (markdown) --- Per-site-switches.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Per-site-switches.md b/Per-site-switches.md index 8447e5d..6a9c20a 100644 --- a/Per-site-switches.md +++ b/Per-site-switches.md @@ -148,7 +148,7 @@ been seen on the page (the number is limited to 99 because of layout constraints This master switch has blocking precedence over dynamic filtering rules and static filters related to script resources. -Furthermore, when JavaScript is disabled through this master switch, [`noscript`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/noscript#Example) tags will be honored on a page (as opposed to when just using filters/rules to block script resources). +when JavaScript is disabled through this master switch, [`noscript`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/noscript#Example) tags will be (tentatively) honored on a page (as opposed to when just using filters/rules to block script resources). The activation of `noscript` tags is done through a workaround, and there might be cases where it's not possible for uBO to mimick perfectly activated `noscript` tags. As with some other per-site switches, the default state of the per-site JavaScript master switch can be set in the [_Settings_ pane](./Dashboard:-Settings), thus allowing to disable JavaScript everywhere by default, and enable on a per-site basis: