Closed Bug 87393 Opened 25 years ago Closed 24 years ago

DHTML layer does not display until screen refreshed

Categories

(Core :: Layout, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: meniscus, Assigned: karnaze)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.1) Gecko/20010607 BuildID: 2001060703 and all previous THis page (http://www.cereberus.com/frameset1.html) contains a layer that is generated via CSS. The background layer has a graphic that is fixed in the lower-left corner, and another layer which contains the page content in front. However, the graphic on the bottom layer does not display unless you "wipe over it" with another window (such as an Explorer window, the mail window, etc). If you "wipe" over part of it, only that part is visible. I have seen this happen on three different computers, all of which have different video chipsets, so it is not a display adapter problem. Reproducible: Always Steps to Reproduce: 1. Simply go to www.cereberus.com and wait for the page to auto-load. 2. Look in the bottom-left corner. You *should* see an image with the "Cereberus" logo, but you probably will not. 3. Move any other application or explorer window over the browser window, or re-load the page, or minimize then restore the browser window. The graphic should then be visible. Expected Results: Graphic should be visible upon initial load.
Confirming issue.
I had to reload the page for the background image to be displayed. The image is being applied to the body element via css: background-image: url(images/background2.jpg); background-attachment: fixed; background-position: 0% 100%; background-repeat: no-repeat;
Status: UNCONFIRMED → NEW
Ever confirmed: true
This bug has been FIXED in the 0.9.5 release-- whatever fixed it may have fixed other CSS/layer/DHTML bugs as well, you may wish to go through and check any bugs similar to this one.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.