New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 599773 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jul 25
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 402376



Sign in to add a comment

Nested divs in full screen isn't exited by calling webkitCancelFullscreen

Project Member Reported by meade@chromium.org, Apr 1 2016

Issue description

Version: 49.0.2623.110 (64-bit)
OS: Linux

What steps will reproduce the problem?
(1)Open the attached file
(2)Click the outer (blue) toggle full screen button 
(3)Click the inner (red) toggle full screen button
(4)Click the inner (red) toggle full screen button again

What is the expected output?
The red div exits full screen, going back to the same state as after (2).

What do you see instead?
The red div stays in full screen (but you can press Esc to exit full screen altogether). Additionally, if you press escape after (4) without clicking the button any more times, the red div remains "full window".



I tested the attached file in firefox, and it behaved as I would expect.



I added logging of document.webkitFullscreenElement, and it looks like Chrome thinks that the red div exited full screen. See below:

(After step 2)
isOuterFullscreen = true full screen element: 
NancyFullscreenBug.html:39 <div id=​"outer_div" style=​"width:​ 700px;​ height:​ 500px;​ background-color:​ blue;​">​…​</div>​

(After step 3)
NancyFullscreenBug.html:59 isInnerFullscreen = true full screen element: 
NancyFullscreenBug.html:60 <div id=​"inner_div" style=​"position:​ absolute;​ left:​ 0px;​ top:​ 0px;​ width:​ 100%;​ height:​ 100%;​ background-color:​ red">​…​</div>​

(After step 4)
NancyFullscreenBug.html:59 isInnerFullscreen = false full screen element: 
NancyFullscreenBug.html:60 <div id=​"outer_div" style=​"width:​ 700px;​ height:​ 500px;​ background-color:​ blue;​">​…​</div>​
 
NancyFullscreenBug.html
2.6 KB View Download
Cc: -mgiuca@chromium.org
Owner: mgiuca@chromium.org
Status: Assigned (was: Untriaged)
Looks like a bug. I'll take a look (though it might end up being a Blink bug and not exactly my area of expertise).

Comment 2 by e...@chromium.org, May 5 2017

Cc: foolip@chromium.org
Still reproduces.
Cc: -foolip@chromium.org mgiuca@chromium.org
Owner: foolip@chromium.org
foolip@ Can I assign it to you? I think this is a Blink issue so you're probably the right person to look at it.

Comment 4 by foolip@chromium.org, May 12 2017

Blockedon: 402376
This is a known issue with the somewhat wacky state of Fullscreen currently, with two meanings of "fullscreen element" that aren't always in sync. This issue is similar to 552541, the problem is described a bit more in  issue 402421 , and I've confirmed that it would be fixed by my ongoing work to reland  issue 402376 .

Therefore, I'll mark this as blocked on  issue 402376 , and verify when that's done.
Status: Fixed (was: Assigned)

Sign in to add a comment