On 05/21/2014 03:43 PM, Gerry Hickman wrote: > Hi, > > In the early days of Netscape 3, I remember being able to "stop" a web > page completely, as in no more HTTP requests, no more looping scripts > and no more frames of animation. > > Many sites constantly generate new HTTP requests bombarding the user > with adverts, div based pop-ups, annoying sounds, videos, animation etc. > > We need the stop button to actually STOP everything. > > Most non-technical web users won't know (or care) what a stop button is, > so they won't care if it's changed. > > In the current SM, the stop button does not seem to work. > > Here's an example of a web site where you can test the issue. Let it run > for over a minute, and look at the status bar, the mouse pointer, and > the stop button itself (flashing). > > http://www.ibtimes.co.uk/wikileaks-reveal-name-mystery-country-having-all-phone-calls-tapped-by-nsa-1449284 >
You might want to check into to this bug report: <https://bugzilla.mozilla.org/show_bug.cgi?id=1008817> (Bug 1008817 - Stop Button/Function inappropriately disabled) Others that may or may not be related: <https://bugzilla.mozilla.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=SeaMonkey&content=stop+button&comments=0> _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
