Skip to main content

Bug Tracker

Side navigation

#14903 closed bug (migrated)

Opened March 21, 2014 07:22PM UTC

Closed October 21, 2014 12:33AM UTC

IE 11 fullscreen inside iframe needs workaround

Reported by: Owned by:
Priority: low Milestone: None
Component: dimensions Version: 2.1.0
Keywords: ie11 Cc:
Blocked by: Blocking:

IE 11 has a bug in its fullscreen support. If the element being made fullscreen is inside of an iframe, the values for offsetWidth/offsetHeight and the results of getBoundingClientRect are 100x too small.

Details of the issue are here:

It's also been noticed that click positions *may* be off by 100x in the opposite direction. I'll update the ticket if we find a repro for that issue as well.

Attachments (0)
Change History (13)

Changed March 21, 2014 07:36PM UTC by dmethvin comment:1

owner: →
status: newpending

Can you add a link to the IE bug you've reported/found at ? If they're addressing this with a slipstream patch there's no reason for us to attempt a fix.

Also if you haven't found a reliable way to correct the numbers (couldn't tell from a quick read) there's nothing we'll be able to do.

Changed March 21, 2014 10:13PM UTC by comment:2

status: pendingnew

The IE bug I've reported is here:

When the error condition is detected (in this case, offsetWidth/Height < clientWidth/Height, which should never happen), the correct numbers are easily obtainted by calling Element.getBoundingClientRect() and multiplying the results by 100, and subtracting .right from .left or .bottom from .top.

Changed April 14, 2014 01:24PM UTC by dmethvin comment:3

status: newpending

Can you post a link to a screen shot showing the problem still exists? Here is what I see on IE 11.0.9600.16659:

Changed April 14, 2014 03:43PM UTC by anonymous comment:4

You have to click the "Click Here" link, and look at the values for offsetWidth/offsetHeight, and the values shown for getBoundingClientRect.

I'll post a screen shot later today, if you still need one.

Changed April 14, 2014 03:50PM UTC by dmethvin comment:5

status: pendingnew

Still puzzled, maybe I'm just not getting it.

Changed April 14, 2014 04:03PM UTC by anonymous comment:6

It's possible that revision has fixed it; I don't have access to a Windows machine at the moment, so I will retest and get back to you later today.

Changed April 15, 2014 02:33AM UTC by comment:7

I can confirm that this still exists in IE 11.0.9600.16659. The screenshot is here:

Judging by the dialog above the screen content, it looks like your second screenshot looks like it was taken from Chrome, not IE 11. If it's IE 11, it has the prompt at the bottom of the screen, as shown in the screenshot.

Changed April 15, 2014 03:04AM UTC by dmethvin comment:8

You're right, I got confused because I was trying to reproduce the issue and can't get anything like you've described. When I run IE11 and go to that page, then click the second "Click Me" link in the box, IE11 goes full screen and shows a prompt but the screen is totally white. I'll try to do a screen recording if that doesn't make any sense but I need to install some software.

Changed April 15, 2014 03:12AM UTC by comment:9

I've seen the "totally white" issue before, specifically on Windows 8 on a Surface. For us, Window 8.1 Update (KB 2919355) released just last Tuesday resolved the "totally white" issue, but left the bad measurements unresolved.

Changed April 15, 2014 07:12PM UTC by dmethvin comment:10

After several updates and reboots I have been able to finally arrive in the same place as you.

I've reported this to the IE team privately to see if they have immediate plans to fix it in a slipstream update. Given that the previous issue was a white screen there seems to be some instability in this area.

Changed April 15, 2014 07:15PM UTC by dmethvin comment:11

component: unfileddimensions
keywords: → ie11
priority: undecidedlow
status: newopen

Changed April 15, 2014 08:12PM UTC by comment:12

Thanks, I appreciate you taking the time to look at it. FWIW, the "white screen" issue was only ever on Windows 8; Windows 7 has been in the current state for a while (some number of weeks), though I don't know how long Microsoft been aware of it.

Changed October 21, 2014 12:33AM UTC by m_gol comment:13

resolution: → migrated
status: openclosed