Closed
Bug 263980
Opened 21 years ago
Closed 20 years ago
background-image: url() leads to page reload in the background
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 106912
People
(Reporter: mozilla, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7) Gecko/20040803 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7) Gecko/20040803 Firefox/0.9.3
if I use background-image: url() within css, this leads to page reload in the
background within a style block, the page get loaded a second time in the
background. A url tag with no content should be ommited.
This is a major bug for Website developers who allow users to change the HTML
code they send to browsers.
Reproducible: Always
Steps to Reproduce:
1. browse to a file with an emtpy url() statement in the css part
Actual Results:
Page get loaded twice
Expected Results:
Load the page once
Comment 1•21 years ago
|
||
(In reply to comment #0)
> A url tag with no content should be ommited.
No, an empty url() value is a relative URI which resolves to the base URI, in
this case the URI of the stylesheet. If you don't want to reload your stylesheet
as a background image, you probably meant background-image: none.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Comment 2•21 years ago
|
||
*** Bug 265799 has been marked as a duplicate of this bug. ***
Comment 3•21 years ago
|
||
*** Bug 272203 has been marked as a duplicate of this bug. ***
Comment 4•20 years ago
|
||
*** Bug 310951 has been marked as a duplicate of this bug. ***
Comment 5•20 years ago
|
||
*** Bug 321090 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Status: VERIFIED → UNCONFIRMED
Resolution: INVALID → ---
Comment 6•20 years ago
|
||
*** This bug has been marked as a duplicate of 106912 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago → 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•