247622 - (stopmeansstop) pressing 'stop' button should not cause a change in display

Status: NEW

(SeaMonkey :: UI Design, defect)

Description

[Max Waterman]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040531 Firefox/0.8.0+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040531 Firefox/0.8.0+

When I am waiting for a page to be displayed, I often feel the need to read the
currently displayed page for longer and so I press the 'stop' button.

I often find that, when I press the stop button, the window's content is changed
- sometimes to a blank page, other times to a partially rendered page.

Please consider changing the action of the 'stop' button to cause the currently
displayed content to be retained, and the results of the partial page rendering
to be discarded.

Reproducible: Sometimes
Steps to Reproduce:
1. Visit a 'slow' web site.
2. Press the 'stop' button before the page has been changed
3.

Actual Results:  
Depending on the progress of the rendering (which depends on many factors;
bandwidth, web page design, etc), pressing 'stop' will change the displayed page.

Expected Results:  
I expect 'stop' to keep whatever it is I am currently looking at.

Comment 1

[jhp (no longer active)]

Affects all platforms, and is not Firefox specific.

Comment 2

[Bill McGonigle (not currently reading bugmail; please contact directly)]

Hardware -> All
Component -> XP Apps:GUI Features (I think...)

Also, sometimes the browser will just go ahead and completely render the new
page anyway.  I set the bug alias to 'stopmeansstop'.

Comment 3

[Phil Ringnalda (:philor)]

I suspect that this is the wrong product/component, but I'm absolutely certain the unchanged assignee/qa is wrong, so -> defaults.

Comment 4

[Serge Gautherie (:sgautherie)]

Filter "spam" on "guifeatures-nobody-20080610".

Comment 5

[Wayne Mery (:wsmwk)]

Max, still see this?

Comment 6

[Max Waterman]

yes, I think I do still see this.