New issue
Advanced search Search tips

Issue 738920 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
jmukthavaram@chromium.org
e...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

CSS containment breaks iframe fullscreen

Reported by a...@scirra.com, Jul 3 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3147.0 Safari/537.36

Steps to reproduce the problem:
1. Visit https://www.scirra.com/labs/bugs/contain-fs/
2. Under "With CSS containment", click "Go fullscreen" in the iframe.

What is the expected behavior?
The iframe should go fullscreen, like it does if you click the example under "Normal".

What went wrong?
The parent frame goes fullscreen instead! It also has a glitch where the element with CSS containment appears solid black, but I suspect that's related to the incorrect frame going fullscreen.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 61.0.3147.0  Channel: canary
OS Version: 10.0
Flash Version: 

In the case with CSS containment, the only change is the iframe is wrapped in an element with contain: strict, so this appears to be what breaks fullscreen.

This does not reproduce in any other browsers, but probably only because they don't support CSS containment.

Comment 1 by jmukthavaram@chromium.org, Jul 5 2017

Cc: jmukthavaram@chromium.org
Labels: -Type-Bug -Pri-2 hasbisect M-61 OS-Linux OS-Mac Pri-1 Type-Bug-Regression
Owner: e...@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Windows 7, Mac 10.12.5 & Ubuntu 14.04 using chrome reported version#61.0.3147.0,stable#59.0.3071.115 & Canary#61.0.3149.0.

Manual bisect info:
------------------
Good build:52.0.2740.0 -Revision-394284
Bad build:52.0.2741.0 -Revision-394609

Unable to run new python script for the above range. Hence providing bisect ingo with old script
Bisect tool info:
----------------
You are probably looking for a change made after 394580 (known good), but no later than 394591 (first known bad).
CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/5364fc6bd081393a667b7aef5ff6766b3b115af1..4d0fe195c0a376db680823555c6be7e7afd68587

Possible suspect:
---------------
https://chromium.googlesource.com/chromium/src/+/1415bcf6ba8f2a2b3b0a9b66e1d0d15fcc66d88a

Eae@Could you please take a look & reassign to the respective owner if it is not related to your change.

Thanks..!!

Comment 2 by a...@scirra.com, Jul 5 2017 

I don't think it's a regression, the bisect just points at when CSS containment was enabled.

Comment 3 by e...@chromium.org, Jul 12 2017

Labels: -Pri-1 -Type-Bug-Regression Pri-2 Type-Bug
Status: ExternalDependency (was: Assigned)
Not a regression and working as intended from an implementation standpoint. The interaction between fullscreen and css containment hasn't been fully resolved yet.

Comment 4 by a...@scirra.com, Aug 29 

This also happens with clicking the fullscreen button on a <video> inside an element with paint containment.

Comment 5 by e...@chromium.org, Oct 23

Cc: e...@chromium.org
Owner: ----
Status: Available (was: ExternalDependency)
►

Sign in to add a comment