On 5/27/14 7:13 AM +0900, Ray_Net wrote:
EE wrote, On 26/05/2014 22:53:
Gerry Hickman wrote:
NoOp wrote:
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)
Yup, that's the same issue. If you browse this site
http://www.theguardian.com/uk
you will notice constant new HTTP requests are shown on the status bar
(or more accurately if you use FireBug). Again, the stop button does not
do anything. These are big name sites; I don't think it's practical for
end users to simply avoid them.
It would appear that the code behind the stop button is from the days
when a web page was just a single HTTP request. I do not believe it's
fit for purpose with today's AJAX based sites..
That site seems perfectly normal to me. Maybe Mac SeaMonkey behaves
differently from Windows SeaMonkey?
WFM too ... perhaps my AdBlock+ avoid activities
The issue is one of confusion. The functionality of the Stop button is
to stop loading a page. It does that quite well. Once the page is
loaded, the stop button has no further function and so should likely be
disabled. As it is left in an enabled state, users can be forgiven for
thinking that it might stop script execution on a fully-loaded page.
Alas, that isn't how it works in my experience. Once the page has
loaded, the stop button has no effect whatsoever on dynamically updated
content.
--
/////////////////////////////////////////////////////////
// Trane Francks tr...@tranefrancks.com Tokyo, Japan
// Practice random kindness and senseless acts of beauty.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
