IE11: Touch Browsing for Today’s Web and Beyond

Internet Explorer 11 in the Windows 8.1 Preview continues the innovative touch support introduced in Windows 8 with new touch features, improvements to existing touch features, and new developer APIs. This blog post showcases just some of the ways touch support in Windows 8.1 with IE11 is even better.

Reliable Hover Menus with Touch

Much of today’s Web was designed with a mouse in mind. In particular, many sites have menus that can only be invoked using mouse hover. The Web should just work for touch, so IE11 introduces support for simulated hover with touch. In many scenarios, it’s ambiguous as to whether a tap should hover or click elements on the pages. To solve this problem, Internet Explorer 11 provides the ability to perform both interactions using different gestures:

  • Tap – click
  • Hold – hover

This video shows the use of hover menus with touch on a few different sites

In addition to touch hover support, a new context menu command bar now appears at the bottom of the screen when you press and hold on a link. This allows for the command bar to display without interfering with the site’s hover menu if there is one. You can also quickly open pages in a new tab or window by accessing the buttons in the command bar.

Improved Link Highlighting

Internet Explorer 11 on Windows 8.1 includes new and improved highlights for fast visual response to your touch. This added feedback helps build confidence in touch by confirming the element you have touched on a page.

This experience is similar to what you’re familiar with on Windows Phone 8, with improvements for some scenarios, like links with CSS transforms. With these improvements, more links are highlighted (including linked images), the highlight no longer impacts the page’s CSS styles, and developers can now use the same markup to opt-out on both desktop and phone:

<meta name="msapplication-tap-highlight" content="no">

The following shows examples of link highlighting in action on IE11, the iPad and an Android device when a CSS transform is applied to the page. Only IE11 wraps the link highlight around link target.

The following shows examples of link highlighting in action on IE11, an iPad, and an Android device when a CSS transform is applied to the page. Only IE11 wraps the link highlight around link target. The following shows examples of link highlighting in action on IE11, an iPad, and an Android device when a CSS transform is applied to the page. Only IE11 wraps the link highlight around link target. The following shows examples of link highlighting in action on IE11, an iPad, and an Android device when a CSS transform is applied to the page. Only IE11 wraps the link highlight around link target.
IE11 iPad Android

Link highlighting with CSS Transforms

<a href="#" style="transform: rotate(45deg)">Links with CSS Transforms</a>

Navigating Back and Forward Using Swipe Gestures

Navigating back to the previous page is one of the most common actions perform by users and comprises about a third of all navigational acts. Internet Explorer 10 introduced the ability to navigate back or forward to the previous page by swiping your finger across the page. Internet Explorer 11 makes the experience faster and more fluid on all devices while preserving memory efficiency and battery life.

To accomplish this, Internet Explorer 11 suspends and caches the previous page to memory when navigating between pages. When you swipe back to the previous page, the page resumes from memory. The result is the previous page is loaded almost instantly when you swipe back. A future blog post will detail how the new page caching works and how sites can be optimized for this experience using HTML5 APIs.

Some pages can’t be suspended. In that case IE11 uses pre-render technology to render the previous page as soon as you start swiping. The result is pages load fast and more reliably.

Back and forward navigation with swipe in IE11

IE11 also improves the experience when using the back/forward buttons. When you press the back/forward buttons, you see a screenshot of the page while the page is loading allowing you to quickly find the site you are looking for as you go back.

HTML5 Drag and Drop with Touch

Touch input should be a first class experience on the Web. Internet Explorer 11 is the first browser to support HTML 5 Drag and Drop using touch, on by default. Drag drop can be invoked using touch by simply pressing and holding. Sites using HTML 5 drag and drop designed to work with a mouse, just work with touch in IE11 — without code specific to touch. Try the Magnetic Poetry Test Drive demo, which was built to show HTML5 drag and drop with the mouse in IE10. It works unmodified with touch in IE11.

Try the Magnetic Poetry Test Drive demo, which was built to show HTML5 drag and drop with the mouse in IE10. It works unmodified with touch in IE11.

Drag and Drop with Touch on the Magnetic Poetry Test Drive page

Direct Manipulation for Mouse, Keyboard, Touchpad and Touch

Internet Explorer 10 delivers industry leading panning and zooming through hardware accelerated direct manipulation. Pages stick to your fingers when you drag or pinch to zoom, even if the page is running heavy script, and the manipulation and animations are always smooth. Developers have a host of APIs to configure the panning and zooming experience in ways you never could before. MSN home page leverages the use of snap points and allows users to swipe through headlines.

Swiping through headlines using touch on

Swiping through headlines using touch on

Internet Explorer 11 on Windows 8.1 brings the same hardware-accelerated pan and zoom technology to mouse, keyboard and touchpad in addition to touch. This allows sites to take advantage of the smooth panning and zooming across all input types. Developers also have the ability for their sites to programmatically trigger pan and zoom through the new msZoomTo() API.

Improved Touch APIs with Pointer Events

We worked with the W3C and other browser vendors to develop a standard for Pointer Events based on the vendor prefixed APIs introduced in Internet Explorer 10, which allow Web sites to support multiple pointing devices including mouse, pen, and multi-touch. The Internet Explorer 11 Preview includes updated MSPointer APIs to reflect the latest Candidate Recommendation specification. The final version of Internet Explorer 11 will support unprefixed Pointer Events.

Touch That Just Works for Today’s Web and Beyond

With Windows 8, we set out to build the world’s best touch experience. Internet Explorer 11 builds on the modern, fast, fluid experience that’s perfect for touch, even for today’s Web that isn’t necessarily designed for touch. With hardware accelerated direct manipulation, pages stick to your finger while panning and zooming for a fluid and natural experience. The browser UI stays out of your way when you start interacting with the page so sites come alive. You can see how developers are using IE’s industry leading standards APIs to build engaging touch experiences including sites like GlacierWorks, Atari, and Contre Jour, as well as examples from the IE Test Drive like Touch Effects and Browser Surface.

Internet Explorer 11 continues to innovate by introducing new touch features and improving existing features to provide the best touch experience yet. Download the Windows 8.1 preview today and see how Internet Explorer 11 is perfect for touch.

Michael Patten
Lead Program Manager, Internet Explorer

Comments (42)
  1. davis says:

    msapplication-tap-highlight? umm why? shouldn't you guys be placing this sort of stuff in the default browser stylesheet so the *designer* can override it with declaration like:

    a { -ms-application-tap-highlight: none }


  2. Arieta says:

    @davis: I imagine once you disabled the tap-highlight with meta, you can still use the standard :hover backgrounds and such, though those only work on block type links not inline ones.

  3. nate says:

    fix this one please

    go to – start searching for something, when auto complete list drops down try to touch an item.

  4. seriously says:

    Microsoft please rip that touch link highlight stuff out right now!!!!

    Not only were people complaining about you adding it in the last 3 blog posts but it ruins the asthetics of many sites.

    Now you are forcing developers of every site in the world to push a meta tag to the browser on every page load to NOT SHOW something!!!!

    In case you've missed what has been happening in web development for the past 10 years here is a tip!

    There are 2 pseudo classes you can apply to all hyperlinks to style them however you please!

    :hover for when a user mouses over (or fake touch hovers) a link


    :active for when a user is clicking a link!!!!! Wink wink nudge nudge!!!!!!!

    So adding your silly verbose IE-only Non-standards nonsense to HTML5 is completely unnecessary!!!!

    In case you missed the memo… touch devices have been around for at least 5+ years now and NO ONE is complaining they don't see extra crud show up on the screen when they click a link… NO ONE!!!!

    Please just stop the nonsense Microsoft and fix the bugs in your browser and dev tools so we can use them. Don't waste time adding silly features for a tablet device you make that you just wrote down nearly a billion dollars on because no one wants it.


  5. nate says:

    also, unless these are improvements that AREN'T in the preview, that touch and hold still doesn't work great on sites. for example

  6. gk says:

    Really requiring meta to disable tap-highlight at page level???

    We should be able to specify this for any link on page (inline or block).

    Please please consider it.

  7. Glenda says:

    Please give us the option for uploading files in IE-mobile, running on Windows Phone. All the modern browsers provide us this functionality.


  8. Mike Dimmick says:

    @Glenda: Use to suggest features for Windows Phone.

  9. Steve says:

    This should absolutely be an *****OPT-IN***** feature NOT an opt-out feature!

    <meta name="msapplication-tap-highlight" content="yes"/>

    Developers of sites everywhere around the globe should not have to tack on 56 bytes to every page load just to get rid of behavior they never wanted (or needed) in the first place!

    This is a horrible idea and it will go down in the hall of fame of other horrible Microsoft Ideas to ruin websites.

    All of these were invented by Microsoft and ALL of them are SHUNNED by developers and standards today

    1) Marquee

    2) CSS Expressions

    3) VML

    4) ActiveX

    5) <wbr>

    6) VBScript

    7) DirectX Page Transitions

    8) Conditional Comments

    9) XML Data Islands

    10) DirectX Filters

    11) Element Behaviors

    12) Smart Tags (and a meta tag to get rid of them!) <meta name="MSSmartTagsPreventParsing" content="TRUE"/>

    13) createPopup (a chromeless popup window only useful to spammy advertisers)

    14) Image Toolbar (again, you had to add a meta tag to get rid of it!) <meta http-equiv="imagetoolbar" content="no"/>

    15) Jump links <meta name="msapplication-task" content="name=Useless;action-uri=…/&gt;

    16) <meta name="msapplication-tooltip" content="This is like the Page Title but with extra wasted bandwidth instead" />

    17) <meta name="msapplication-navbutton-color" content="#ffaacc" /> Lets let developers mess with the browser chrome! This worked so well when we let them mess with scrollbar colors – Not!


    All of these Microsoft IE inventions died. Some quicker than others.  Do we need to unset the smart tags or the image toolbar any more? NO! because Microsoft saved us the agony of doing so by removing the feature completely in the next release.

    We are begging you to do the same here. Remove this feature before it hits RTM or if you absolutely insist on adding it make it an OPT-IN feature NOT and opt-out!

    As others have pointed out hyper-links can be styled to an incredible degree with CSS deeming this feature completely moot to start with!

    Please call up Chris Wilson, or Eric Lawrence, or anyone else well respected in the Web Browser development community if they think your opt-out meta tag is a good idea for this redundant "feature".  Bet you can't find a single person that thinks this is a good idea.

    @Michael Patten please sit down with @Dean H. and have a serious discussion about these kinds of things before committing them to code and worse yet documenting them on the IE Blog!

  10. pmbAustin says:

    Why not support the "hold with one finger, tap with second finger" to pop-up context menus?  Isn't this how Win7 did things?  It was easy, unambiguous, and intuitive.  Why drop support for that gesture?

  11. Martijn says:

    "Improved Link Highlighting"

    Great, but please disable link highlighting for mouse input. This is the very reason I ended up adding this to my trusty reset css:

    a:active { background: none; }

    Because when clicking (yes, CLICKING, not just tapping) a link it gets a gray background, which is ugly, unwanted, annoying, and breaks design.

  12. Darryl says:

    Why does the IE11 Preview developer tools show me attributes in my DOM that are not there!?

    None of my <td> elements contain a noWrap, rowSpan, or colSpan attribute (and they never will.. cAmElCaseIEAttributes died over a DECADE ago!

    None of my <table> elements contain a cellSpacing or cellPadding attribute (again, NO ONE uses camelCase – stop that nonsense Microsoft!

    None of my <form> elements contain an encType attribute!

    In my styles I see TD, BODY, FORM etc CSS style declarations – yet I have NEVER used (nor ever will use) upper case element selectors!

    What kind of doctype is: "<!><!>"???? again, stop the insanity Microsoft! Not only is is wrong and ugly – it is NOT what I specified!

    WTF!? is an </input> tag? such a closing tag doesn't exist! check the W3C specs Microsoft… self closing tags are FORBIDDEN from having child elements or a closing tag (script is the only odd exception due to a bug IE introduced decades ago)

    Why are all the CSS properties defined inline on my elements showing up in UPPER-FLIPPING-CASE???? I did not serve up:

    <div style="PADDING: 2px; OVERFLOW-Y: auto;">

    I also did not add spacing around my properties, values or delimiters.  DO NOT SHOW ME **YOUR** interpretation of what I served up.

    Please, please, please… in this one case… copy the living daylights out of Firebug and Chrome's dev tools – they far exceed your tools by an order of magnitude!

  13. Martijn says:

    Tap&hold to "hover" is wrong. It's so wrong, guys, please remove it, it's so incredibly uncommon and unintuitive. Tap&hold is used to drag elements. Every respectable mobile OS handles dragging by tap&hold, so, Microsoft, you are not the one to dictate otherwise. All this will do is force developers to make workarounds to reverse this silly behaviour, and handle dragging properly. Come on guys, just do what the other browsers to. Conform for just freaking once.

    Users will understand, trust me, they will. They WILL understand that a touchscreen has no hover state. Except when using an active digitizer stylus. Those things can hover perfectly fine. Ever thought of that?

  14. Martijn says:

    Also, "reliable hover menus" are a thing of the past. Any self-respting website does no longer rely solely on the hover state for navigation. When a web developer makes something like that, the customer quickly comes back with the issue "I can't navigate it on my iPad" and it's fixed a couple of days later.

    We don't need solutions for problems that have been fixed years ago. Get with the program. Windows 8 is not exactly the first touch-capable OS, and neither is IE11 the first touch-capable browser by any measure.

  15. Georges HK says:

    Will the final release of IE11 also support the Pointer Lock API?

    It's a must for gaming.

  16. Easter Bundy says:

    Please make all menus and ribbons in desktop mode also hover, because that would be totally awesome! Go Broncos!

  17. @Steve: That's indeed an impressive list. But I think you're missing the larger point here: Nothing breaks, and the highlight will be the default behavior that users grow accustomed to with IE11. If users don't like it, think it's stupid, etc, etc, they're going to blame the browser and consider an alternative. There's really no reason any site should bother opting-out via the meta-tag, and if anything, you're probably right that support for controlling the feature should be removed.

  18. If this were limited to anchor elements with href's, I think it'd be fine. But I believe I'm seeing this behavior in the Win 8.1 Preview on a <img> element with an onclick handler. The problem in my case is that the tap on the image fades the current image out and fades another in. The flash of gray over the entire image is very annoying in this slide-show application.

  19. @Steve, Seriously – what we found (and heard from users) was that much of the web does not provide proper touch feedback through CSS styles (or provides extremely subtle feedback that may be occluded by a finger), which presents an issue for users in their ability to confidently target links with touch.  Most modern touch enabled browsers provide a similar experience, as shown in the screenshot above, and similar vendor prefixed opt-out methods.  Unfortunately, there’s not yet a W3C standard way for opting out across browsers today.

    @Martijn – we heard this feedback in IE10. Now, IE11 only does highlighting for touch input.

    @nate – touch hover is a feature of the immersive browser's touch first experience.  I found the feature works on If you're still seeing the issue in the immersive browser, let me know. We're working with Amazon on a solution for the search suggestions issue.

    @Ted Johnson – Totally agree. This is something we're considering tweaking for the final release of IE11.  

  20. Adam says:

    @Jacob Rossi [MSFT]

    I have a Microsoft Surface RT AND a Surface PRO… both upgraded to the Windows 8.1 preview.

    I can say with 100% certainty that the new highlight feature is annoying and does not mesh with the theme of any site I visit.

    I hope you don't intend to keep this behavior as there is no Chrome browser available for Metro that I can switch to if this becomes the final version.

    Can you at a bear minimum change the behavior such that if a CSS style declared by the site/game/app is in place that you'll turn the ugly grey Microsoft highlight off automatically.

    As a developer this sucks. I now have to go update my apps to add a meta tag to ensure my customers don't get stuck with this when 8.1 rolls out as final. I'm not happy about this at all.

  21. @Adam – Do you also dislike the highlight on other touch browsers? If not, is there something specific about IE11's implementation that you dislike?  

  22. Arieta says:

    By the way guys. Since many people complain about how tabs wait a few seconds after closing to rearrange (so you can clickclickclick to close multiple tabs easier): make the tab lengths animate, instead of just popping into place. Perhaps that would look better.

  23. Christof Höke says:

    Regarding Hover menus on hold:

    There is a major problem with this approach: DISCOVERABILITY. How should a *user* know when to just click or when to hold?

    On a lot of websites the main menu is a list of items with dropdown/flyouts on hover. But in most cases not all have flyouts, just some. In any case the user hovers over every item and views the opening flyout or clicks to go to a page. The hover on hold approach would mean the user need to know if there is a flyout to open or not. And this for me seems VERY difficult to do…

    Also as others already pointed out, no other platform does this, so it is even more unusual.

    In IE10 we had the aria-haspopup="true" for this kind of popup/flyouts which actually works beautifully. Of course this needs to be told to developers. But to "teach" developers is much easier than to "teach" users to learn a completely new and unexpected behaviour.

    To recap:

    I am sure quite some thought got into the hover on hold idea but please reconsider or at least comment:

    – hover on hold is undiscoverable for website users, how should this work?

    – IE10 aria-haspopup="true" does/did work, why drop that completely?

    I quite like the recent development of IE including the new F12 but this issue is a bit strange to say the least.


  24. Iviak says:

    @Jacob Rossi [MSFT] I think there are 2 problems with the Microsoft implementation.

    1. It sucks for developers that want to override this behavior since it is an opt-out not an opt-in issue

    2. Is sucks for end users (because developers are not going to take the effort and waste bandwidth to fix it) and the users end up with an ugly grey background on everything they click – like since when has grey ever been a remotely sexy color? Find me a designer that would choose gray for a primary color? grey is the "black & white" past of design. Pick a color, any color! Just not grey! (hint – every other browser uses a nice, pretty shade of blue… the base color of a standard hyperlink)

    however even if you pick a better color than gray – please change this into an opt in behavior and|or make sure that if a designer has provided a CSS hover|active style that you do not interfere with the designer's choice.

  25. demo fail says:

    Microsoft you've just proven you are playing "Astronaut Architecture" with this feature. Highlighting the bounding box of a link is fine because 99.9999% of the time links are rendered horizontally.

    The gray is also quite ugly as many have mentioned as are the chamfered corners. You might have missed this in design 101 class because you were absent but nothing in nature is perfectly square.  Rounding the corners provides a softer more touch inviting interface.  Sadly Windows 8 and everything that you've forced into IE10 & IE11 just looks so amateur as if your designers realized that they could never compete with other software so you just gave up and went in the complete opposite direction when windows phone started… Oh wait the original IE on windows phone couldn't do border radius! Now it all makes sense!

  26. That Guy says:

    Get rid of the RETARDED METRO BUTTONS in the developer tools, it's actually now officially THE most obnoxious thing about IE11 besides the fact that the GUI can't be customized at all.

    Also if you actually decide to ever fix IE's toolbars (a big reason why I move people OFF of IE) the favorites bar belongs to the RIGHT of the command bar. Also the file menu belongs on TOP! Also the command and favorites toolbars belong ABOVE the tabs AND the address bar, the addres bar belongs ABOVE the tabs, this means that OUR controls put *US* in control, not the content they represent.

    Implement those fixes and IE's GUI won't suck any more and I might actually not switch people.

    Oh yeah, and support the HTML5 audio and video elements for goodness sakes! Proprietary codecs and "only if installed manually" codes mean IE does NOT support the HTML5 audio and video elements PERIOD. Start listening to people because Microsoft in general has been wildly out of touch with the tech world in general.

  27. Igor says:

    Will HTML5 accessibility support increase in IE11?  This is quite a useful resource:


  28. Arieta says:

    Noticed an odd thing today that has been there since IE7 at least. If a page requires username/password to visit (like a router logon, or an FTP, something that without the password throws a 401 error), you cannot navigate off of the page while the password field is up.

    Additionally, if the connection is slow and the password field launches while you are on another tab, IE becomes entirely frozen (it works, but you cannot interact with it anyway) and you have to close the browser from the task manager. This last one might be IE11 exclusive.

  29. Lolz says:

    Some whine about few meta data add ins, yet webkit is hell with all its prefixes and non standards markup.

  30. pmbAustin says:

    One of the BIGGEST issues I have with the touch browser (i.e. no mouse, no keyboard, using the Surface only) is scrolling.

    There are a LOT of sites with very "long" pages… some, like Facebook and Twitter, can essentially be "infinitely long".  

    The problem?  There's no fast way to move around such a page.  I find myself endlessly 'scrubbing' or 'flicking' trying to scroll back up to the top, or down to the bottom.  It's tedious and time-consuming and annoying.

    With a mouse, it's simple… grab the scroll bar "thumb" and drag.  Quick and easy.  There is NO equivalent solution for the touch-only environment.

    Touch-capable Safari on iOS has one simple gesture that solves half the problem… touch the status bar at the top to "zoom to the top".

    Obviously the Metro IE11 doesn't have any chrome to touch like that, so there ABSOLUTELY NEEDS TO BE a set of gestures to allow easy page navigation.  While you get ultra-thin little scroll bars with a little 'thumb' to show you where you are on the page, it's apparently impossible to "grab" that thumb via touch, in order to drag it.  At least I've never managed it.

    One possible solution would fit in with the concept of "semantic zoom".  Right now if you pinch small, there's a lower limit beyond which you can't "zoom out" any more.  It would be nice if, once you hit this level, you could pinch once more and get a "total zoom out", to a complete representation of the page on the screen, very tiny.  Then you could easily touch the top or bottom to zoom there… or anywhere in the middle.  There might be issues with some VERY long pages, but it'd still be an improvement.

    Short of that, if there were some much faster way of scrolling to top and bottom (two finger dragging?), or even an app-bar button "top of page, bottom of page") would be useful, if not super convenient or intuitive.

    We really REALLY need a solution to this.  I'm surprised it's not a bigger issue for others.  It's major missing UI/end-user functionality, IMHO.

  31. @pmbAustin – Thanks for the feedback. This is definitely something we've heard from users and we know it can be a pain point, particularly in long documents.

  32. BlindProgrammer says:

    This is off topic but please look at these bugs too if you have the time.

    Why does IE 11 keep asking me to disable addons even though the sum of the time that my addons take does not exceed the threshold in the "Disable addons" dialog box? I have 4 enabled addons. The first two take 0.01 seconds and the last two take 0.0 seconds. The threshold in the dialog box is set to 0.20 seconds. I don't know about you but 0.01 + 0.01 + 0.0 + 0.0 = 0.02 which is not greater than 0.20. And by the way, why do you display times in this strange two-digit way: 0.20 and not simply 0.2.

    Also, the Addons dialog box is buggy when you use it with the keyboard. Firstly, the combo box which allows you to filter the list of displayed extensions is not working properly and requires that you press enter before the filter is applied. Secondly, the "Get more dictionaries" button link in the "Spelling correction" section, once pressed it is removed, an action  which makes the dialog box unusable with the keyboard.

    Bring up the Addons dialog box and

    1. Press alt+t to choose the "Toolbars and Extensions" radio button and then tab to the Filter combo box. Press alt+down to open the combo box and choose an option using up/down, say "Downloaded controls". Tab to the extensions list and observe that the filter was not applied. Only if you press enter after choosing an option in the Filter combo box will the filter be applied. This is in contrast to all other combo boxes found in Windows!

    2. Choose the "Spelling correction" radio button. Tab to the "Get more dictionaries" link and activate it using space or enter. Observe that the button becomes disabled and the dialog box becomes unnavigable using the keyboard because the developers forgot to put focus on another control after they removed it. Please read…/208005.aspx in order to find out how to fix this problem.

    And while fixing it, please tell the Windows Explorer team to fix the same bug which occurs when trying to unblock a file that has been downloaded from the Internet.

    Download a file from the Internet and find it in Windows Explorer. Press alt+enter to bring up the file's Properties dialog box. Activate the "Unblock" button and observe that the dialog box becomes unnavigable. Same issue.

    These bugs exist in Windows for years. There are many more keyboard bugs of course, which I don't have time to list neither do I know any official way of reporting them.

  33. Gamer says:

    Интеренет Эксплорер говно)))

  34. Eric says:

    I come for the information but stay for the crazy!

  35. Arieta says:

    Found another bug in the Win7 preview, this one is recurring… it happened in the IE10 win7 preview as well, and was fixed on IE10 final, now its back in IE11 preview.

    If you go to fullscreen mode (press F11), the top bar with the tabs, buttons, etc, will not appear when moving the mouse to the top of the screen.

  36. Tommy says:

    @Arieta, you just miss the link to connect ticket where I can vote?? Or are you the one confusing comments section with bug reporting platform?

  37. Real McCoy says:

    Dear IE team,

    What is the "wisdom" behind not hooking the Ctrl+0 for zoom to normal, when 0 is pressed on keypad. The same shortcut works when the 0 is press on keyboard number row!

    Do you guys use Firefox? Few years back, they introduced this shortcut Press and hold Ctrl and click with mouse on the browser back/forward button it will open the corresponding page in new tab. Today, all the known browsers except IE support that shortcut. It is a very must have useful shortcut believe it or not.

    And yes, its being ~2 years since I posted the feedback:…/one-missing-and-another-poorly-implemented-shortcut

    If there is any room for few tweaks, please add it in your catalog for IE11 release. Because the next time IE team will listen and push "real feature updates" (as opposed to security updates), will be the time we would be asked to buy a new version of Windows. Show some love for human being.

    ACID tests:

    Believe it or not, IE11 preview (both Metro and Desktop) fails Acid2 test Please fix it.

    On Acid3 test, if you press on A of Acid while pressing shift, it shows you result. The result suggests that both IE10 and 11 on Windows 8, RT and 7 are less than perfect.

    I hope someone in IE team hate these fact as much as I do!

    Thanks for your consideration.

  38. Hello! Here, I still hope one tab feature: "Refresh this tab group".

    Currently running a Windows Blue (8.1), still I do not see this feature… I have asked this a long time already since Internet Explorer 10 development stage. I hope very much, and my fingers are crossed here in Finland.. that someone key employee hears my feedback. 🙂

  39. @Real McCoy says:

    Acid 2 is not current anymore and not a real conformancetest either.

    For a current up to data javascript conformance test you should go to:

    You can compare modern browsers javascript conformance there.

  40. @@Real McCoy says:

    Acid2 is testing browser's layout rendering engine capabilities (in case of IE, its Trident) as well as JS engine.

    Acid2 is performing well on IE9+, FF3+, Chrome10+, Safari 4+ and Opera 8+.

    So something is definitely broken in IE11's layout rendering which is causing the problem.

  41. Provash says:

    I want to free download Internet Explorer version 11

  42. Gérard Talbot says:

    @Real McCoy and @@Real McCoy

    There has been a spec change regarding clearance and margin collapsing; such part of the spec is rather pretty difficult to understand and to explain. And so, apparently, complying with such spec change would break acid2 test.

    More info:…/margin-collapse

    Gérard Talbot

Comments are closed.

Skip to main content