49773 - The stop button is grayed out even though it is still active

Status: VERIFIED FIXED

(SeaMonkey :: UI Design, defect, P3)

Description

[Chris McClelland]

The stop button is grayed out even though it is still active. When going to 
www.nbc.com, the pages scrolls very slowly, pressing stop (even though it's 
greyed out), fixes this. Goto bug 49751 for more info.

Comment 1

[jlarsen]

:)

Comment 2

[Chris McClelland]

opps, using build 2000082108

Comment 3

[Asa Dotzler [:asa]]

over to layout.

Comment 4

[Kevin McCluskey (gone)]

Dividing up claytons bugs to triage.

Comment 5

[Doron Rosenberg (IBM)]

stop button does not grey out for me on win98 2000090504. Scrolling is 49751

Comment 6

[Kevin McCluskey (gone)]

This is really a UI problem. The stop button should be deactivated when it is 
"greyed out" but it isn't.

Changing component to browser. Reassigning.

Comment 7

[Asa Dotzler [:asa]]

XPApps?

Comment 8

[sairuh (rarely reading bugmail)]

or...networking? cc'ing tever.

Comment 9

[Marcel Blokpoel]

Another thing - when Java/Javascript thingys are running, waving flags and that
kind of gadgets, stop button is also greyed out but still works to stop them.
Stop button greys out as soon as loading the page is finished, irrespective of
other things that may be running.

Comment 10

[Jacob Kjome]

Marcel's point can be seen very well in the following example:

http://www.narain.com/gecko/

load the page and as soon as you see the (DHTML) icons moving across the 
screen, click the grayed out stop button.  Now the images quit loading and a 
white background is painted wherever icons are/were.  The script itself isn't 
stopped, just Mozilla's ability to continue to load/display images and repaint 
the background on this dynamic page.

Jake

Comment 11

[Marcia Knous [:marcia]]

Netscape Nav triage team: this is a Netscape beta stopper.  reassigning to 
mcafee - can you please analyze?

Comment 12

[Blake Ross]

The button still works when it's disabled because it's incorrectly using 
onclick, which doesn't check for disabled.  It should be using oncommand; that 
will get fixed as part of bug 30878.

Comment 13

[Viswanath Ramachandran]

Blake - do you know how to fix this - in that case, please take the bug. thanks,
Vishy, McAfee. 

Comment 14

[Blake Ross]

Okay, taking just to fix the case that the button still works when disabled.

Comment 15

[Jason Eager]

Please don't fix this until you make it so that the stop button isn't
deactivated UNTIL everything (and I mean everything,
rendering, flashing graphics, etc) is completed. I've gotten out of some knotty
situations by taking advantage
of being able to click on the stop button even though it is deactivated.
(Examples: That damn "blinking line" bug,
very slow rendering, etc).

Right now this is more of a feature than a bug.

Comment 16

[Blake Ross]

Fix checked in.

Comment 17

[sairuh (rarely reading bugmail)]

works fine at www.nbc.com. tested with:

linux comm 2001.05.02.08
mac comm 2001.05.02.09
winnt moz 2001.05.02.12