@Quest: If you think of "permission" as whether "script", "object",... are checked or not:
barbaz wrote: ↑Wed Jun 12, 2019 12:55 am
The actual effect is more like "Block subdocuments from having more permissions than their top document".
Meaning:
Without the option selected - subdocuments have just whatever permission you've set for their domain/site.
With the option selected - subdocuments are only allowed the permissions that are allowed for BOTH the top-level site AND whatever you've set as allowed for the subdocument's site.
-----
While I'm here, I should also point out that the use of the word "Cascade" to describe this feature is particularly confusing for NoScript Classic users. Look at how it was used there:
And also around the forums, e.g. in the sticky -
viewtopic.php?f=7&t=8309
Cascading has always referred to cascading "allows", never cascading "denys". People think by word association, you can't just abruptly invert the association of a word like this without causing confusion. And putting "Cascade" as the first word, puts the emphasis on "Cascade", but it seems the emphasis was intended to be on the word "restrictions".
Now look at my suggested wording "Block subdocuments from having more permissions than their top document", and how the restrictSubdocScripting option was worded in NoScript Classic -
Would be much less confusing, wouldn't it? See?
@Quest: If you think of "permission" as whether "script", "object",... are checked or not:
[quote=barbaz post_id=100413 time=1560300909 user_id=181509]
The actual effect is more like "Block subdocuments from having more permissions than their top document".
[/quote]
Meaning:
Without the option selected - subdocuments have just whatever permission you've set for their domain/site.
With the option selected - subdocuments are only allowed the permissions that are allowed for BOTH the top-level site AND whatever you've set as allowed for the subdocument's site.
-----
While I'm here, I should also point out that the use of the word "Cascade" to describe this feature is particularly confusing for NoScript Classic users. Look at how it was used there:
[img]https://noscript.net/noscript/screenshots/noscript-screenshot-options-advanced-trusted.png[/img]
And also around the forums, e.g. in the sticky - https://forums.informaction.com/viewtopic.php?f=7&t=8309
Cascading has always referred to cascading "allows", never cascading "denys". People think by word association, you can't just abruptly invert the association of a word like this without causing confusion. And putting "Cascade" as the first word, puts the emphasis on "Cascade", but it seems the emphasis was intended to be on the word "restrictions".
Now look at my suggested wording "Block subdocuments from having more permissions than their top document", and how the restrictSubdocScripting option was worded in NoScript Classic -
[img]https://noscript.net/noscript/screenshots/noscript-screenshot-options-advanced-untrusted.png[/img]
Would be much less confusing, wouldn't it? See? :)