Closed Bug 36944 Opened 25 years ago Closed 25 years ago

empty CSS background-image:url('') on BODY hides page completely

Categories

(Core :: CSS Parsing and Computation, defect, P3)

Product:
Core
Component:
CSS Parsing and Computation
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: aheck, Assigned: harishd)

References

(
URL
)

Details

(Keywords: css1, Whiteboard: [nsbeta3+][Fix in hand])

Attachments

(2 files)

Attachment that works without a problem.
1.69 KB, text/html
Details
Proposed patch
765 bytes, patch
Details | Diff | Splinter Review
If you visit www.sector-x.de with M15 you get just a empty black page. There are some errors in the CSS definitions of the page (checked with w3c css-validator). Maybe Mozilla should ignore them, if they are broken or return some kind of error message (would be a cool feature for webdesigners).
Since the page works when saved to my disk or loaded from my web server, I'm going to call it a dup of bug 36871 (sites that use etag don't display properly and sometimes crash). Bug 37208 (nonexistant stylesheet --> nothing displayed) might also come in to play. *** This bug has been marked as a duplicate of 36871 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Bug 36871 got fixed, and this page is working slightly better, but it's not quite fixed yet. I'm going to un-dup it for now because I can't figure out what's causing it. I'm also going to cc the guy who fixed 36871 in case he missed stylesheets when fixing it. - Nothing displays in browser. If you alt-tab out and back, you do get a black background (does that implicate bug 11491?). - Saved version displays correctly - Saved version loaded from local webserver dispalys correctly - Displays correctly in composer
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
the page does not load at all, server error. Waiting for a day or so to see if the site comes back on.
Tested with Build # 2000051920 on RH 6.2. Was able to reproduce this bug everytime. Also checked with NN for site errors. Works with NN. Checked page source, Black is page background. Images are not being displayed.
Tested with Build #2000051920 on Windows 98 SE. Problem is worse in Windows than Linux. Erratic behavior. Sometimes the XUL for the Nav-bar is displayed in the browser window resulting in a second non-functioning Nav-bar, sometimes the blank black page is superimposed on top of the second Nav-bar. Was able to reproduce one of the two problems everytime.
<body style="background-color:#000000 ; background-image:url('')"> ^^ This is what causes the problem. Insert _anything_ between the quotes or remove the background-image property altogether and the page works. Confirming bug, changing component to Style System and Platform/OS to All/All. Also adding some appropriate keywords.
Status: UNCONFIRMED → NEW
Component: HTML Element → Style System
Ever confirmed: true
Keywords: 4xp, css1, nsbeta3
OS: Linux → All
Hardware: PC → All
Summary: Website www.sector-x.de doesn't work at all → empty CSS background-image:url('') on BODY hides page completely
Moving to my list for triaging.
Assignee: rickg → harishd
Could you please create an attachment that could reproduce the bug? I'm not able to reproduce this from my local drive [ will attach the working test case ].
Status: NEW → ASSIGNED
It sounds more like networking than style system! CCing Mark and Gagan.
Reassigning to gagan ( as a result of triaging Clayton's bug list ).
Assignee: harishd → gagan
Status: ASSIGNED → NEW
Harish: it appears that you are passing an empty string to NS_NewURI and the return value is being ignored. We should check for this early on. which would mean your area so back to you.
Assignee: gagan → harishd
This is so strange. With a break point ( inside the debugger ) the above URL renders. This could be some sort of a timing problem ( I suspect view manager ).
Status: NEW → ASSIGNED
CCing Kevin..for input.
Attached patch Proposed patch — — Splinter Review
Whiteboard: Fix in hand.
Target Milestone: --- → M18
Such a simple change! Should we nominate for nsbeta2 since it is fixed?
We can...but according to Kevin this might require...extensive testing. I think , to be on the safer side, we should hold this off till beta3.
Marking nsbeta3+...
Whiteboard: Fix in hand. → [nsbeta3+][Fix in hand]
Using NS_VMREFRESH_NO_SYNC instead to of NS_VMREFRESH_IMMEDIATE per Kevin. That fixes the problem. MArking FIXED.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Marking verified per last comments.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: