Closed Bug 298954 Opened 19 years ago Closed 19 years ago

images specified in css continue downloading after "stop" button is hit

Categories

(Firefox :: File Handling, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 291172

People

(Reporter: worried, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Images specified in CSS are not equated into the download progress bar. Also, if
you hit the "stop" button, data will still be loaded from css. 

Reproducible: Always

Steps to Reproduce:
1. Write some css that will use a network socket to access a large file
BODY{ background-image:URL(http://domain.com/a-very-large-image.gif)}
2. write an html page to load that css, eg:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
	<title>CSS Testing</title>
	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
	<link rel="stylesheet" href="/path/to/your/css/style.css" title="default style"
media="all" type="text/css" />
</head>
<body>
	<p />
</body>
</html>
3. Access the html file in firefox, hit the "stop" button, and watch the image
continue to download

Actual Results:  
the image continues to load, thus hogging bandwidth

Expected Results:  
It should have stopped loading the image when the stop button was hit.
Does the problem still occur with a current trunk build from:
<http://www.mozilla.org/releases/nightly.html>
(In reply to comment #1)
> Does the problem still occur with a current trunk build from:
> <http://www.mozilla.org/releases/nightly.html>
also exists on the nightly build.

*** This bug has been marked as a duplicate of 291172 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.