CSS: Don't workaround the IE 11 iframe-in-fullscreen sizing issues

IE 11 used to have an issue where if an element inside an iframe was put
in fullscreen mode, the element dimensions started being 100 times too small;
we've added a workaround that would multiply them by 100. However, the IE 11
issue has been unexpectedly fixed and since our detection was really detecting
the browser and not a bug, we've started breaking the browser instead of fixing
it.

Since there's no good way to detect if the bug exists, we have to back the
workaround out completely.

Refs ff1a0822f72d2b39fac691dfcceab6ede5623b90
Refs fb9adb9f0511ac2993e664697aa26e97d0a4d213
Fixes gh-3041
Refs gh-1764
Refs gh-2401
Refs 90d828bad0d6d318d73d6cf6209d9dc7ac13878c

diff --git a/src/css.js b/src/css.js
index f96600b451553c2feb80e6709be2830d4b12cd71..e222ce7b42f54934554cd35b8d96b0f0eb7c5ed5 100644 (file)
--- a/src/css.js
+++ b/src/css.js
@@ -186,19 +186,6 @@ function getWidthOrHeight( elem, name, extra ) {
                isBorderBox = support.boxSizing &&
                        jQuery.css( elem, "boxSizing", false, styles ) === "border-box";
 
-       // Support: IE11 only
-       // In IE 11 fullscreen elements inside of an iframe have
-       // 100x too small dimensions (gh-1764).
-       if ( document.msFullscreenElement && window.top !== window ) {
-
-               // Support: IE11 only
-               // Running getBoundingClientRect on a disconnected node
-               // in IE throws an error.
-               if ( elem.getClientRects().length ) {
-                       val = Math.round( elem.getBoundingClientRect()[ name ] * 100 );
-               }
-       }
-
        // some non-html elements return undefined for offsetWidth, so check for null/undefined
        // svg - https://bugzilla.mozilla.org/show_bug.cgi?id=649285
        // MathML - https://bugzilla.mozilla.org/show_bug.cgi?id=491668