Instead of "Advised" and "Dangerous," the language could read "Better Security" and "Not Advised."
Even "Advised" and "Not Advised" would be better phrasing. Most instances of javascript found in the wild aren't dangerous, and users don't have the information required to determine why javascript might be dangerous. They seem to find this confusing.
Instead of "Advised" and "Dangerous," the language could read "Better Security" and "Not Advised."
Even "Advised" and "Not Advised" would be better phrasing. Most instances of javascript found in the wild aren't dangerous, and users don't have the information required to determine why javascript might be dangerous. They seem to find this confusing.
Does "Not Advised" correspond to the default setting here? If so, users are rightly confused that we ship something that we mark Dangerous, and if we change it to Not Advised, then they will be confused that we ship something and then mark it 'Not Advised'.
Once the security slider controls the global NoScript behavior, maybe NoScript's own "Allow scripts globally" UI should simply be hidden instead of rephrased? Or did I miss a usecase for this button?
Once the security slider controls the global NoScript behavior, maybe NoScript's own "Allow scripts globally" UI should simply be hidden instead of rephrased? Or did I miss a usecase for this button?