Updated Per site switches (markdown)

Raymond Hill 2023-05-08 16:24:21 -04:00
parent c1dbd9d4db
commit d0284ceb62
1 changed files with 1 additions and 1 deletions

@ -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. This master switch has blocking precedence over dynamic filtering rules and static filters related to 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. 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: 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: