For sites that don’t fit in any of the 3 aforementioned presets, you can choose to use CUSTOM permissions: CUSTOM is not a preset, but a way to give very specific permissions to a site, applying to that site only.In the NoScript 10 we’ve got 3 presets (DEFAULT, UNTRUSTED and TRUSTED): you can assign one of them to any site, and the sites with the same preset share the same set of (configurable) permissions.Since it was anyway impossible to replicate exactly the well known user experience provided by NoScript 5.x (which, BTW, is still actively maintained and available here), I’ve tried to find a silver lining in the forced rewrite, taking it as a chance to incorporate user feedback collected over more than 12 years, especially about making the permissions system more customizable.Īnd indeed, the old concepts are all still there, but the way they are implemented is more flexible and amenable to customization, albeit admittedly less discoverable and, for long time users, surely confusing at least initially.īugs aside, I think the biggest problem with the transition, which I’m truly sorry for, is me not having found the time yet to write any proper user-oriented documentation for NoScript 10 but maybe we can start here by providing a minimalistic overview, mapping the new “Quantum” UI onto the “Legacy” (I actually prefer to call it “Classic”) one: The ones who know better about recent history of Firefox and of its add-ons ecosystem are aware, though, that the UI couldn’t stay the same simply because the technical foundation (XUL/XPCOM) for the “old” one is not there anymore, and NoScript has been forced into being completely rewritten as a WebExtension (and therefore its UI as pure HTML) or just die. Someone seems to be still convinced that changing our beloved NoScript UI has been a whimsical (and suicidal) decision of mine, entirely avoidable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |