New issue
Advanced search Search tips

Issue 756471 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Aug 27
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Fullscreen sized iframe body getBoundingClientRect() returns incorrect left and top offsets.

Reported by mi...@infogr.am, Aug 17 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36

Steps to reproduce the problem:
1. Create a page with iframe that has allowfullscreen attribute
2. Make that iframe go fullscreen (with javascript code)
3. body (element inside of iframe) node's getBoundingClientRect() top, left properties return wrong values

What is the expected behavior?
Expected would be that body (inside fullscreened iframe) getBoundingClientRect() top, left properties would return 0. Safari, Firefox it works like that.

What went wrong?
body element (inside fullscreened iframe) getBoundingClientRect() top, left properties return numbers taken from I don't know where.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 60.0.3112.101  Channel: stable
OS Version: OS X 10.12.6
Flash Version:
 

Comment 1 by mi...@infogr.am, Aug 17 2017

Actually this also did not work on the same Chrome version in windows 7.

Comment 2 by woxxom@gmail.com, Aug 17 2017

Can you upload a test html that exhibits the problem?
The attached test html works correctly for me in both Chrome and Firefox in Windows 7.
test.html
1020 bytes View Download
Components: Blink>JavaScript>API Blink>Fullscreen Blink>Layout
Labels: OS-Chrome OS-Linux OS-Windows

Comment 4 by mi...@infogr.am, Aug 18 2017

Sorry! Here is more precise example.
fullscreen_from_iframe_body.zip
1.5 KB Download

Comment 5 by mi...@infogr.am, Aug 18 2017

In last example it does not matter if iframe parent document.body has scrolling enabled.
Labels: Needs-Triage-M60 M-62
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Mac 10.12.6, Win-10 and Ubuntu 14.04 using chrome reported version #60.0.3112.101 and latest canary #62.0.3189.0.

This is a non-regression issue as it is observed from M45 old builds. 

Hence, marking it as untriaged to get more inputs from dev team.

Thanks...!!

Comment 7 by e...@chromium.org, Aug 21 2017

Components: -Blink>Layout -Blink>JavaScript>API
Owner: foolip@chromium.org
Status: Assigned (was: Untriaged)
Labels: M-69
Status: Fixed (was: Assigned)
Fixed with top layer changes in Chrome 69.

Sign in to add a comment