Quote:
Originally Posted by crxssi
Does anyone know a way to get Firefox to block Javascript animation without breaking javascript completely???
I *can't stand* things moving on my screen while I am trying to read. Adblock, of course, is a mandatory start. The Flashkiller plugin works great for stopping Flash. And Firefox has a built-in way to disable GIF animation. But more and more sites are using Javascript to somehow create unwanted, constant or intermittent movements, animations, scrollings, and slideshows that I can't stop or even block.
|
crxssi, I completely agree with you.
I switched to GNU/Linux mainly because I think the user should be enabled to decide what our computer exactly does or does not.
WE MISS A *SELECTIVE* JAVASCRIPT FILTER.
It could be a FireFox/Iceweasel add-on.
It could be a modified version of FireFox/Iceweasel, with an improved javascript engine, with added switches for executing instructions.
It could even be another browser, redesigned to give back control to the user.
At the moment, I'm using Iceweasel (Debian's Firefox) with disabled Gif animation, Flashblock, Adblock. And Prefswitch, which I think is useful but incomplete, for the same reasons that you already pointed at. I also resize the browser's window to avoid to see the annoying moving crap.
A fast improvement of Prefswitch could be adding a "CTRL+something" keyboard shortcut for fast on/off switching, but the perfect solution should be a selective javascript filter that blacklists the javascript single commands that I don't want my computer to execute (even on a keyword basis).
The same applies to NoScript: selective code blocking capability.
To the first users, the task of experimenting and finding-out-the-code. To the others, simply a copy-and-paste operation.
Maybe we should look around to see how many people feel the same need:
1) make a single webpage addressing the problem, and
2) thoroughly spread the argument around the net (Linux community, Firefox and Iceweasel developers, Add-on developers, or whatever)
Please keep us informed if you find any solution to this relevant (and still unsolved) problem...