565933 - "Stop loading this page" button does not stop loading page.

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Oliver]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3

When I click a link on the popular news aggregator Drudgereport.com, often the servers hosting the linked pages become overloaded due to the increased traffic coming from Drudge. When a page is taking too long to load, I will give up and hit the Stop button. However, more often than not, hitting the Stop button causes the browser to jump to a blank or partially loaded page, and then it stops loading that page. When I hit Stop, I want it to stop where it is. 

Reproducible: Always

Steps to Reproduce:
1. Go to drudgereport.com
2. Click links till you find one that takes more than 15 sec. to load.
3. Hit the "Stop loading this page" [x] button.
Actual Results:  
Instead of stopping, the browser jumped to a blank or partially loaded page and then stopped loading that page. 

Expected Results:  
It should have stopped attempting to load the new page and stayed on the Drudgereport page.

This is a small problem, but it is really irritating, and it seems like it should be fairly simple to fix.

Comment 1

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html

Comment 2

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.