Closed
Bug 557363
Opened 15 years ago
Closed 15 years ago
window.stop does not stop a binary file download once the server has replied
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: ashusta, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_8; en-US) AppleWebKit/533.2 (KHTML, like Gecko) Chrome/5.0.342.7 Safari/533.2
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100315 Firefox/3.5.9
Documentation at https://developer.mozilla.org/en/DOM/window.stop
Once a remote server has replied to an HTTP request to begin a download, but before that download is complete, the window.stop method fails to abort the in-progress download.
In OS X watching the 'net panel in Firebug shows that the connection remains open until the file completes downloading.
In MS Windows monitoring network activity using Fiddler2 also shows that the download is not stopped.
Reproducible: Always
Steps to Reproduce:
1. Create a script that will load a large image or other file that takes a long time to download.
2. After the large file has begun to transfer, but before it finishes, call window.stop();
Actual Results:
In your network monitoring tool of choice, observe that the network connection to the server is not dropped.
Expected Results:
The network connection should be dropped.
Component: General → DOM: Core & HTML
Product: Firefox → Core
QA Contact: general → general
Comment 1•15 years ago
|
||
window.stop() stops things that are loading in a given window.
File downloads via the external helper app handler are not attached to a particular window once it's been determined that they need to be handled external to the browser.
So I'm not sure why window.stop would do anything with them (and indeed it does not).
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•