Rendering of "height=100%" element inside table cell broken in IE8 compatibility mode

Confirmed Issue #11295665 • Assigned to Hamza A.


Christian J.
Mar 16, 2017
This issue is public.
Found in
  • Internet Explorer
Found in build #
Reported by 45 people

Sign in to watch or report this issue.

Steps to reproduce

The latest IE11 security update KB4012204 introduces a regression bug (maybe due to included fix KB4015241) with element height calculation in table cells in IE8 compatbility mode / DOCTYPE HTML 4. If an element has its height set to 100% and the parent table / row / cell has an explicit or inherited height, then the element should size itself to the parent cell instead of only to its content.

I’ve attached an example HTML document showing this issue. Rendering is correct when forcing IE11 standards mode or in Edge, Chrome or Firefox, but in IE8 compatibility mode the DIV only covers its content and not the entire height of its parent cell.

Version: 11.953.14393.0
Update Versions: 11.0.40 (KB4012204)


Comments and activity

  • Changed Steps to Reproduce

  • This also happens with the other mixed modes:

    This breaks legacy apps and causes a lot of problems for many end users and developers, as seen in:

    I have also attached a second repro that showcases the problem with an iframe.

    The iframe may be a bit special due to the 150px min height most browsers enforce in this scenario (iframe in a table). IE now enforces it as max-height which is incorrect.

  • I concur that this is a huge issue; several of our large ERP customers already have to face the choice between rolling back the entire Windows update and blocking it (including two months worth of security fixes) or switching to a different browser altogether.

    Apparently this update even breaks some versions of Microsoft’s own Dynamics CRM product line, so there’s hope this one will be escalated appropriately.

  • Agree, we’re scrambling to make updates here and could have to make sweeping changes as a result.

  • Microsoft Edge Team

    Changed Assigned To to “Ke X.”

  • Thank you for the bug report. Passing on to the right team to look at IE11 issues.

  • Also, test with various doctypes (HTML5, XHTML 1.0 Transitional) and not just HTML4

  • Microsoft Edge Team

    Changed Assigned To from “Ke X.” to “Brent M.”

    Changed Status to “Confirmed”

    Changed Assigned To from “Brent M.” to “Hamza A.”

  • We are also experiencing this issue, and it is seen as a huge issue to our customers.

    Rewriting our code to avoid this issue is a gigantic and unrealistic task.

    Hope this issue has a high priority and is fixed ASAP.

  • This issue also appears to affect the SharePoint 2010 Report Viewer Webpart (IE8 compatibility mode)

  • Same problem with 3 of our web products …hope MS fixes soon. Only current solutions is to tell customers to use Chrome or Firefox…a big deal for some.

  • This affects IE11 in compatibility modes only, so if you can move to Edge mode, this will be alleviated. The following may do the trick for some cases ``

  • @Marin B. - I am sure many of us are in the same situation, we are dealing with customers on various iterations of browsers and Windows, and changing to Edge mode breaks many parts of our site across versions while this breaks a much smaller number and is limited to newest IE11. Working around this issue or, more ideally, Microsoft issuing a fix is the more practical solution.

  • What is the timeframe for a fix for this? I have several production systems that are impacted.

  • Same here - I have production websites that are seeing an impact from this issue. Would be very nice to get a timeframe for a fix.

  • I can confirm that update KB4016635 fixes the issue for Windows 10! Thanks for pointing it out!

    So far it seems a manual download and install are required, as the update doesn’t appear to be included in the official Windows Update rollout yet. Also note that this update doesn’t increment the version of IE11 - it just fixes the rendering issues - so looking at IE’s About page is not enough to determine whether the update has been successfully installed.

  • We are having the same issue on production server.

    Any update?

  • The fixes have been released and are public available the catalog:

    Windows 10 Version 1607:

    Windows 10 RTM Version 1507

    IE11 on Windows 7 and Windows 8.1

    Please keep in mind, that the packages for Windows 10 are full cumulative Updates and do not have Prerequisite for their installation.

    The packages for Windows 7 and Windows 8.1 are different, as they 1 just contain the DLL from the rendering-engine and needs to be installed on top of the March IE-Update KB4013073 for Internet Explorer.

  • Thanks for the fixes. We are good to go as well.

  • We distributed the links above and are finding that the download links seem to be throwing errors.

    Any idea on what’s going on here?

  • We are able to fix the issue after applying below latest updates.

    Windows 10 Version 1607:


  • Is this still a fix that must be manually installed or has it been released with a windows update to automatically install.

  • Just as Jarrod R. asked - Is this still a fix that must be manually installed, or has it been resolved through the normal Windows Update process?

  • @Reed C, the update was packaged and sent out by Microsoft. It was in the April update

You need to sign in to your Microsoft account to add a comment.

Sign in