Open
Bug 714809
Opened 13 years ago
Updated 2 years ago
CSS background-image not displayed, page turns white when entering DOM fullscreen mode
Categories
(Core :: General, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: b.oomens, Unassigned)
References
()
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7
Steps to reproduce:
To test it's possibilities I've created a FullScreen API demo over at: http://jussay.in/testcases/fullscreen/ and used a background-image on the <html> node that covers the full screen (via background-size). The icon in the right upper corner triggers fullscreen mode.
Actual results:
When clicking this icon the page enters fullscreen mode as it should...yet the background-image disappears and the background turns white.
Expected results:
It should display the background-image correctly instead of showing just a white background.
PS this is my first (browser related) bug report so if I am doing something wrong...please do tell ;)
|
||
Updated•13 years ago
|
Component: General → Untriaged
QA Contact: general → untriaged
|
||
Comment 2•13 years ago
|
||
Thanks for the testcase! I won't claim to understand css backgrounds, but I noticed that if I remove "background-size: cover" the image is displayed...
Blocks: 545812
Component: Untriaged → General
Product: Firefox → Core
QA Contact: untriaged → general
Summary: Page turns white when entering fullscreen mode (FullScreen API) → CSS background-image not displayed, page turns white when entering DOM fullscreen mode
Version: 11 Branch → Trunk
|
||
Comment 3•8 years ago
|
||
I ran into a very similar issue in reveal.js. When I fullscreen the slides the background image goes away.
I made a reduced test case:
https://blog.wanderview.com/bg-image-bug/
I was able to work around the problem by doing document.documentElement.requestFullscreen() instead of document.body.requestFullcreen().
Anne suggested there might be a spec issue here:
https://github.com/whatwg/fullscreen/issues/40
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•