> If the user wants to invoke/allow the feature
And when there are hundreds of features... Scratch that. Even if there are ten features, the user will simply click "allow all" without paying attention to what's requested.
Re:Introducing chrome.scripting
by canada_dry on Wednesday June 09, 2021 @11:04AM
(#27448740)
Yah, this is the conundrum of security vs. useability.
More and more Android has been lumping disparate access permissions together with the goal seeming to be KISS.
It would seem like a useful compromise to have harmful features/functionality disabled by default for each new script - controlled at the individual script level.
If the user wants to invoke/allow the feature, they should be able to explicitly and manually enable it. Like the android app permissions: Allow access to x? [none, this time or always?]