David E. Ross wrote:
It seems that the Stop button does not work on long-running scripts, including malformed JavaScript. When I encounter this, I use PrefBar to disable JavaScript.
A similar approach would be in using NoScript to block all scripts as a default, and then granting access to individual scripting only as needed.
On a lot of sites (especially media ones), there's a lot of scripting going on. Some of it is necessary for getting to the content that you want, but there's quite a bit of scripting that's used to deliver graphics, animation, advertising and other eye-candy, as well as quite a bit that's essentially usage tracking.
In my own usage, I tend to leave scripts from places like Google Analytics, Google Tag Manager, Facebook, Amazon, etc. blocked unless I'm having problems getting a page to display correctly. Conversely, scripting hosts that have "CDN" in the name tend to be "content delivery network", and often mirrors of the content you want. On the other hand, I've learned to identify a number of scripting hosts that are ad delivery networks, and have found that it's generally safe to permanently blacklist.
The one challenge for selectively enabling scripting hosts is that for some, there's a cascading effect. Sometimes, the script (and scripting host) that is needed for the content you want is actually delivered through another scripting host. Thus, if you go to site A, and enable their scripting, you may also have to enable scripts from site B, and in turn, site C, before you get the content you want. But if you're blocking several other scripts, it may be worth it, of having less tracking, less animation, and less hung scripts.
Smith _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
