![]() That way it looks cleaner and the "default" option won’t confuse a new user with the "untrusted" option. Personally, I think you should bring back the default behavior of the previous Noscript that just runs passively in the background like it used to (if you haven’t already) and remove the "default" button. If the user of Noscript is supposed to chose whether to trust or blacklist a script, what is the point of even showing a "default" option? We wouldn’t want to go back to the default option anyways once we’ve chosen. ![]() The default was having nothing to do with a script unless we trusted it or blacklisted it. I like having a blank slate you could say and I don’t like something slipping past me when I never wanted it makes sense and all, but why is it an option? Pre-webextention, Noscript blocked EVERYTHING. Some nitpicky stuff would be if you could have the drop down menu show when you hover over the icon and if you could possibly remove the default whitelisted domains and let the user choose what they want to whitelist. I get that you can fine tune your default to fit your needs, but everyone was fine with the previous method and, with no disrespect to you, if you really want to fine tune everything, you’d probably have a better time using Umatrix with its easier to manage UI where you can see every domain without having to click to each one and changing them. It just seems like unnecessary bloat to have the "default" option and the "untrusted" option. You either block a script all together it or you don’t block it at all. It hangs before I can do anything.Īlso, is there anyway you could just remove the "default" option? I liked it better when it was black and white. Any reason why that is? All I do is go to it. ![]() Also, a bonus, on Arch Linux the packager backported that preference to Firefox 57, so nice of them, which made everything work almost as well as in the pre-57 days.When I go into the Options menu, Firefox will freeze up and I have to force close it through Task Manager. Fortunately a patch is in Firefox for a future version that adds the option "ui.context_menus.after_mouseup", which makes the right-click menu work like on Windows. The FoxyGestures developer mitigated this problem by making right-menu take 2 clicks to trigger as an option enabled by default on Linux, but that can be annoying as now the regular right-click menu doesn't appear when you expect. That stopped the gesture in their tracks. There's nothing you can do about this regardless of the gestures add-on you use - life is worse due to security concerns, this is why we can't have nice things, etc.Īnd 2nd on Linux (maybe Mac too) Foxy Gestures did not work at all by default since the right-click menu triggers on mouse down, not mouse up. This means stuff like about:blank, when a page fails to load, preferences pages, and Mozilla's add-on site. It does have 2 issues - 1st it does not work on special pages due to security restrictions. It has right-button+move-in-a-pattern gestures, as well as "chorded" right/left clicks and wheel gestures. This was more of a pain than NoScript, but after trying a few I switched to "Foxy Gestures" and I'm mostly happy with it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |