Exploring Device Orientation and Motion

Today, we released a prototype implementation of the W3C DeviceOrientation Event Specification draft on HTML5Labs.com. This specification defines new DOM events that provide information about the physical orientation and motion of a device. Such APIs will let Web developers easily deliver advanced Web user experiences leveraging modern devices' sensors.

How This Helps Developers

With the Device Orientation API, developers can explore new input mechanisms for games, new gestures for apps (such as “shake to clear the screen” or “tilt to zoom”) or even augmented reality experiences. The prototype’s installation includes a sample game to get you started in understanding the API.

Video showing the concepts explained in this post in action

How This Works

The Device Orientation API exposes two different types of sensor data: orientation and motion.

When the physical orientation of the device is changed (e.g. the user tilts or rotates it), the deviceorientation event is fired at the window and supplies the alpha, beta, and gamma angles of rotation (expressed in degrees):

Diagram showing the alpha, beta, and gamma angles of rotation returned in the deviceorientation event related to 3D X, Y, and Z axes: alpha = rotate around the Z axis, beta = X axis, and gamma = Y axis.

<div id="directions"></div>


window.addEventListener("deviceorientation", findNorth);

function findNorth(evt) {

var directions = document.getElementById("directions");

if (evt.alpha < 5 || evt.alpha > 355) {

directions.innerHTML = "North!";

} else if (evt.alpha < 180) {

directions.innerHTML = "Turn Left";

} else {

directions.innerHTML = "Turn Right";




When a device is being moved or rotated (more accurately, accelerated), the devicemotion event is fired at the window and provides acceleration (both with and without the effects of gravitational acceleration on the device, expressed in m/s2) in the x, y, and z axis as well as the rate of change in the alpha, beta, and gamma rotation angles (expressed in deg/s):

Diagram illustrating the gravitational acceleration on the device returned by the devicemotion event in the x, y, and z axis.

<div id="status"></div>


window.addEventListener("devicemotion", detectShake);

function detectShake(evt) {

var status = document.getElementById("status");

var accl = evt.acceleration;

if (accl.x > 1.5 || accl.y > 1.5 || accl.z > 1.5) {

status.innerHTML = "EARTHQUAKE!!!";

} else {

status.innerHTML = "All systems go!";




Trying Out The Prototype

You can download the prototype at HTML5Labs. This prototype requires Internet Explorer 10 running on devices with accelerometer sensors supported by Windows 8. The prototype works as an extension to Internet Explorer on the desktop, where developers can get a first-hand look at the APIs. To get started building your own pages with the prototype, all you need to do is install the prototype and then include a reference to the DeviceOrientation.js script file (copied to the desktop after installing the prototype):

<script type="text/javascript" src="DeviceOrientation.js"></script>

We Want Your Feedback

We want to hear from developers on this prototype implementation of the W3C Device Orientation Event Specification, so please let us know what you think by commenting on this post or sending us a message.

—Abu Obeida Bakhach, Program Manager, Microsoft Open Technologies Inc.
Jacob Rossi, Program Manager, Internet Explorer

Comments (62)
  1. Arieta says:

    Dear IEBlog,

    When can we test out IE10 on Windows 7?

  2. tem says:

    why tracking protection list is not sync beetween computers in Windows 8?

  3. acidcode says:

    @Arieta: Forget about it, they'll never comment on this.

  4. gabriel morrow says:

    im starting to think they are abandoning the idea of ie 10 on windows 7

    etherway it will help firefox and chrome overtake ie

  5. Remy Sharp says:

    You can also try it out on devices that *don't* have accelerometers using a polyfill like http://remote-tilt.com </end-self-pimp>

  6. IE10 technologies says:

    Coupling this device orientation technology with HTML5 WebGL will produce great things.

    Kudos to the IE team!

  7. Jacob Rossi [MSFT] says:

    @Remy Sharp – Nice idea!  Looks like lacks either the unprefixed or -ms prefixed version of CSS 3D transforms (possibly a couple other minor things, but that's what struck me first). So it's not quite working in IE10 yet.  See: http://bit.ly/JMf3Tk

    For basic testing on devices that don't have accelerometers, the HTML5 Labs prototype will let you simulate the motion/acceleration using your mouse.  Though it doesn't go as far as remote control like yours–cool stuff!

  8. Kevin says:

    I have been using IE10 for a while with Consumer Previous Windows 8… I find my biggest complaint is flash. It is only reliable maybe 50% of the time… often sound appears but there's no video, sometimes it works but it is completely unreliable and therefore I have to have Chrome available in case… the other thing I've noticed unlike the other browsers is, even if I have one tab open sometimes I'll click on a link and then the whole page will be white (and no, it's not the typical thing where the PC is freezing, in fact I have an I7) – I have to close IE10 and relaunch the same page… if I stay on the same tab and hit refresh or type in a different URL the page stays white. On other browsers, this never happens… please fix these two things! I always like to have the latest versions but these 2 things are constant and very annoying.

  9. @Kevin says:

    Consumer Preview? You mean "the thing" that's actually obsoleted by the Release Preview and the RTM Version? o.O

    Actually, I haven't had any of these problems either on the RP or on the RTM.

  10. Edward says:

    You describe this stuff like it is new… You realize we've been using this on iOS, BlackBerry, and Android for ages now… IE is always the last one to the table.

    It's probably because you've been working so hard on fixing the IE blog comment form right!

    Or we're you busy getting rid of the flash list in IE10 so that desktop PC users (99.999% of your market) can actually use flash in their default browser?!

    #WindowsMetro #CensoringFlashContent #DoomedToFail

  11. Prior Semblance says:


    It's a specification draft….

  12. JO says:

    Why is IE10 metro not working properly on popular free porn sites like redtube.com (not working) and youporn.com (sometimes working).

    lacking support for such questionable but undoubtedly very popular sites will make IE10 very inpopular with websurfers.

    Especially male ones…

  13. robert says:

    The image is not at all clear and unambiguous. The rotational arrows for the x and z axis can still be interpreted as clockwise or counter-clockwise depending on the way you look at it (or how someone's brain works, appearantly.)

  14. Philip says:

    @Edward, IE10 has built in flash. IE10 desktop for Windows 8 and Windows 7 will render flash on all websites. The Metro (Windows 8) version will render flash from the websites which are white listed. In iOS, flash is not supported. In Android's upcoming update JellyBean is also dropping Flash support. By the end of October when Windows 8 will be released for General Availability and JellyBean would be arrived, among Android, iOS and WindowsRT; IE10 metro would be the only tablet browser supporting Flash (providing the webmaster/site-owner verify the low-power device compatibility, touch support and orientation support and submit their website to Microsoft for whitelisting).

    Secondly, this technical blog article is not saying its a "new stuff" but only telling people how to build websites using upcoming W3C standards in Visual Studio which will work on IE10 and other browsers. The W3C draft is still yet to approved for w3c-recommendation. In the link provided in the first line of this blog, W3C being the official body is stating:

    "This section describes the status of this document at the time of its publication. Other documents may supersede this document."

    This is a "prototype implementation" which is subjected to change at any phase. So does the iOS, Blackberry and Android version. Real developers don't get comfortable with the feature which is yet to signed by W3C. Because they know what happened to CSS3-Gradient when IE team was waiting for W3C's recommendation, and other browsers (Firefox, Chrome, Safari and Opera) provided the same "tentative" implementation while IE was sticking with their proprietary DX filters (introduced in 1997). Eventually, when the recommendation was published (in later 2011), W3C chose the other candidate implementation which all non-IE browsers ignored. As a result, many websites are running the non-standard vendor-prefixed code and those browsers would have to support the non-standard and standard for a long time! IE10 dropped the DX filter support and implemented a clean non-prefixed version of gradient following the W3C recommendation.

    So, its not a "new stuff" it is a "future stuff" from W3C standards point of view.

    Finally, it has been said and observed over and over again; once a troll, always a troll – no matter whatever is presented to them.

  15. Frank says:

    First thing… Fix this god damn blog! Holly schmit why is it so hard to post a comment! even legacy asp has a fix for this bug – just apply it for Pete's sake!!!

    @Philip Metro IE will not be the only tablet running Flash… All existing android tablets still have it and the BlackBerry PlayBook will continue to run it.  In fact if you've used a tablet that supports flash you get the full web experience… When you switch to iOS you keep hitting roadblocks. "here's a demo of how this works ______" where the user gets nothing because Apple blocked flash due to Steve Jobs having one of his classic temper tantrums like a 2 year old.

    Users that don't see flash are the ones that suffer… No audio, no video, no special fonts, no simple file uploads, no camera, no video, no microphone.  Oh sure the web is catching up and HTML5 is *begining* to enable all of this bit it's a 5 year turnaround at best.

    What shows the developer community and the end users that Microsoft doesn't care is having proper flash support built in and then disabling it by default!

    Let's call a spade a spade… Microsoft has created a censorship list and unless you are willing to pay the hefty entry fee you don't get to play.

    This is 1,000% against the free and open web that the rest of us are working towards!

    Sadly it is the end users (billions of them) that suffer and they have no say in this process… Heck most of them have no idea that when they upgrade their default browser will no longer play all their flash content… And the developers that would at least like to be able to detect this and force them to jump over to the non-metro version CAN'T!!!! Because Microsoft is refusing to provide a property/method for JavaScript to detect when users accidentally opened the 1/2 browser and need to switch to the full browser.

    Classic Microsoft IE Management Incompetance Again!

  16. Yannick says:

    @Frank – IE10 just doesn't support Flash competlly but is that a reason to say its against an free and open web?

  17. Andrew says:

    @Yannick the web is about free.  Free as in beer as well as free as in speech.

    "Content designed for the web should work in any browser on any platform on any device"

    Any browser,

    Any platform,

    Any device.

    This has been the Mantra of the web since it started.

    Microsofts decision to censor the Web is now in stark contrast to this.

    No longer will flash content just work… Desktop users everywhere suffer a bad Internet experience in Metro IE because Microsoft wasted time building a censorship list for flash before consulting anyone in the developer community. When they announced it here on the blog they had already painted themselves in a corner because although it was instantly proven to be a horrible idea they were to late to pull it out of the RTM release.

    As developers we know where all the failure points are.

    1.) using waterfall instead of agile

    2.) adding features without consulting with any of the customers (users or developers) is asking for trouble, and now they are extremely upset

    3.) developers are notorious for over engineering so not only is the process done wrong (whitelist vs user defined blacklist) but because so much effort was wasted doing it Managment is weary of pulling it out because that confirms it was a failure officially

    Now that Microsoft has announced and released this mess on developers and users alike they've gone completely silent.  They refuse to even discuss the subject and hope that over time it will go away.

    Unfortunately it will only get worse over time as users start using IE10 and realize that Microsoft ruined their default desktop browser experience in order to provide their new tablets with better battery life.  Yes that's right.  Wreck 99% of your existing paying users experiences in order to potentially improve the experience for 1% of your future customers.

    Needless to say your existing customers (that know what's going on with Metro IE) and the developers that are aware of these changes are totally pi55ed off and Microsofts silence only makes it worse.

    The professional thing to do at this point would be to admit your mistake, talk openly with the community about why you embarked on this mission, where you over stepped and how in the future you won't make huge descisions about the future of your browser when it affects millions of people without informing the community before its too late to reverse the changes.

    You've been called out dozens of times since you posted about the flash censorship list… When are you planning to address the users and developer community?

    I agree with Eric Lawrence [MSFT] completely, the lack of responses from Microsoft Management to the major concerns expressed by developers makes the whole IE team look bad.  This was one of the biggest reasons why Chris Wilson left and Microsoft has obviously failed to resolve it.

    Your developer community deserves much better.

    Much, much better.

  18. Yannick says:

    @Andrew – And that's howe it is on iOS and Android, actually, Windows 8 is the only mobile OS that still supports Flash (partial in Metro, but you can switch to desktop and then: tada)!

  19. Andrew says:

    @Yannick yes but you're missing the point.  Ignore tablets completely… When millions of PC users "upgrade" their PCs they will be thrown into Metro whether they like it or not… And when they launch IE they will NOT have proper flash support!!! This is a DRASTIC change for PC users that have expected flash to just work on their PCs for the past 10 years!

    I think you'd be amazed just how many sites use flash it is way more than you think.

    Thankfully Microsoft knows that users want to ruin their desktop browsing experience by using Metro IE.

    I don't think Microsoft realizes just how furious developers and users are about this change. Every day I talk to someone about Metro IE they are flabbergasted when they discover that Microsoft is actually trying to do this.

    I haven't met anyone (ANYONE!) that thinks this scheme makes any sense at all. I must have discussed this with 70-80 developers and users so far… Almost everyone quotes that Microsoft is "F___ing nuts" and to be honest at the moment with this wall of silence and ignoring developers I can't help but feel the same way.

  20. AndyCadley says:

    There is something deeply ironic about web developers now complaining that IE's reduced support for a completely non-standard and proprietary technology, i.e. Flash, is now breaking their sites. If you have ever complained about IE not following standards, then I'm afraid you no longer have the right to throw stones. Web Developers are increasingly getting exactly what they asked for and the fact that turns out to make their life harder is kind of tough luck.

  21. George says:

    @Everyone who is butthurt about the CV List on Immersive IE: Desktop IE will be present even on Windows RT. Confirmed 3 days ago. This means that every Windows device is Flash-capable. Users can be redirected to the Desktop version of IE10 by implementing a simple HTTP Header (X-UA-Compatible: requiresActiveX=true) or META Tag (<meta http-equiv="X-UA-Compatible" content="requiresActiveX=true" />).

    This makes Windows 8 the only OS which can run Flash on any Tablet device. Jelly Bean does NOT support flash, Key Lime will not support Flash either. I also agree with AndyCadley – I must add that we must not endorse the usage of non-standard technologies.

  22. Philip says:

    @Frank, IE10 is not released as GA yet. JellyBean will be available this month. So all the NEW Android tablets and Apple's old/new tablet won't be running Flash. And all the NEW and OLD Windows tablet run flash. Only exception for NEW tablet is that the webmaster need to verify the power and touch capability of their app to the living standards of tablet. So among Windows, iOS and Android; only Windows IS NOT TERMINATING flash support in tablet.

    BTW there will be many Win8 tablets (with powerful Intel ci5 processor) with pro version which will support desktop version too. And desktop version of IE10 for Windows 8 and 7 supports flash as well without the CV restriction.

    @Andrew, all true.. but are you trolling at Google's or Apple's blog too who already have terminated the flash support OR (are you exclusively hired for anti-MS trolling)?

  23. Neuro says:

    @Philip Perhaps Andre's "trolling" here because he doesn't care about tablets? Windows 8 is also an desktop/laptop OS and it makes no sense to limit it by whatever are the requirements and limitations of the tablet hw. Or, not for the customers – of course Microsoft is trying to leverage their desktop domination to bootstrap the app offering on their new tablet OS, which makes sense for them (or their marketing department anyway), but some of us refuse to play the game. It's like if OS X would boot to iOS emulator by default.

    Now you're going to tell me that no one is forcing us to use the Metro IE, which I guess is right… but then why the OS boots to Metro?

  24. @Neuro says:

    The Start Screen does not equal Metro (I assume you mean Modern UI).

    It's just a live-tile-based Start Menu, which gives you access to the Desktop in one click.

    Also, Immersive IE was designed keeping power efficiency in mind, but Desktop IE is free of any limitation.

  25. Clark says:

    The BlackBerry PlayBook plays full flash and has one of the highest HTML5 scores available on a tablet (so stop saying IE is the only one!)

    As for the ability to switch/or force users to the desktop version of IE vs the Metro mode version (and please for the love of god stop calling it immersive mode!!) losing the users session in the process is 100% unacceptable and a major usability issue.

    What developers are angry at is that Microsoft controls access to this list, it's costly in terms of time and resources in order to qualify for the list, and even after doing so it may take up to 3 months!!! To he on the list this if you submitted today you might not get accepted until DECEMBER!!!!

    Which part of this process makes any sense?! Why are PC users suffering because Of Microsofts design flaw?!

    @Dean [MSFT] you should have listened to @EricLaw [MSFT] about including this in IE and announcing it when it was too late to pull it out before shipping RTM!

    Now developers are angry at Microsoft (both externally and internally in the IE Team!)

    Best of all this silence on the issues is soooo helpful in restoring our confidence in Microsoft/IE!

    For now we are telling all of our clients that Metro IE is not supported at all.  It sucks but Microsoft won't listen to developers any more.

  26. @Clark says:


    Not Metro. Microsoft doesn't call you Michael, so don't change the name of their products.

    Also, you can first tell us BlackBerry's share in the tablet market, then tell us whether we'll get Flash 11.4 or 12 on it.

  27. Daryll says:

    @@Clark – the current share of windows tablets worldwide is ZERO PERCENT! So you're trying to back up your argument with null.

    Microsoft violated patents by using both "Metro" and "immersive" this neither name will be part of their marketing for Windows h8.

    I think they should call it "plain flat rectangles and squares with no gradients, lighting effects, shadows, 3D effects, or rounded corners – so everything looks incredibly ugly" mode.

    Actually the consumers end up naming it and so far they call it "squaresville" or "plainsborough" not too surprising when you put zero effort into designing an intuitive user interface.

    As for the actual word "immersive" it implies a mode that you get totally absorbed into and become one with.  Considering the new interface looks like a mockup screen that was never finished most can't even get out of the criticism mode long enough to even consider it as the final "you're stuck with this mess" screen.

  28. Internet Explorer is opening every .mp3 in media player and i want the user to download this file instead of opening.

    I cannot modify headers. Please share some trick if any.

  29. @Daryll says:

    Actually, it might be already 0.00003% since I know a couple of people (including me) who use Windows 8 on a tablet. But joking aside, you KNOW that Windows tablets WILL have more market share than the PlayBook. Citing Wikipedia: "Much of the 700,000 units shipped to retailers remained on the shelves for months".

    How does Immersive violate any patent? Immersive IE10 as in "no toolbars, no menus, no controls visible, just the user and the HTML document"; Immersive != Tiles… Actually, IE is the only Immersive app so far. If you fail to get that, then I feel sorry for you.

    "Incredibly ugly" – that's pretty subjective. I find the interface quite appealing and I'm glad Microsoft got rid of Aero, since it was simply a memory hog. If you want eye candy, there are plenty of third party options. Also, Windows 7 will be supported until 2020, so you have plenty of time to find "viable alternatives". And if you're not happy with Microsoft, you have other options (though I doubt your productivity would actually be any better).

    Anyway, I know it's useless trying to make you use your brain efficiently. It appears that you're always the same b*tthurt guy, just posting under different names on this blog. And I'm frustrated that this blog does not allow flagging for spam, since you annoy interested readers.

    @ashutosh khanna – Right-click the link to the mp3 and select "Save target as…"; that will allow you to choose a folder where to save the mp3.

  30. Michael says:

    If Metro is no longer the valid name due to trademark infringement then please let us know what the new name is!  Although I can't see how "immersive" can be patented (let alone how it applies) I would like to know the correct name so I can reference it correctly.

    There has also been a lot of talk about the lack of favorites in (formerly known as metro) were they seriously omitted? This seems like a massive failure as I use my bookmarks 6-10 times a day easily.

    Lastly all this talk about the Big Brother flash list never clarified if this was just an IE thing or if it was tied to the networking stack (e.g. wininet.dll)?  We want to make sure that Microsofts usability failure is only limited to IE and that Chrome and Firefox for (formerly known as metro) are still 100% flash compatible and not limited by the "Microsoft Censorship List"[TM]

    I'm actually quite happy IE is making this major stumble as it provides more ammunition to software vendors and websites to help push people off IE onto more capable, predictable browsers with less bugs.

  31. @Michael says:

    Metro is the name of the design language. It was used internally by Microsoft until before the RTM. It's Microsoft's tradition that code-names are dropped in the final release of the product (Chicago, Whistler, Longhorn, Moorea, Vienna, etc. – do any of these tell you something?) There is no official statement that the change of name was due to trademark infringement. Also, the new name is "Modern UI"/"Modern-style apps". Why should Microsoft patent the word "Immersive"? Microsoft isn't Apple (and I pray to God it will keep itself this way).

    No, favorites were not omitted. If you had been as interested in reading this blog as in bashing Windows 8 everywhere, you would have known that; from another post:


    To add a site, click the pin button and select "Add to Favorites".

    To remove a site, either:

    1. start typing its name in the location bar. Then right click it and select "Remove".

    2. click the location bar and scroll to the right of "Frequent" sites; you have your "Favorites" there. Right-click the one you want and select "Remove".


    Also, Flash support is browser-specific; you would have known that if you hadn't been trolling most of the time. Google and Mozilla have already announced that their Modern-style browsers would have the same level of support for Flash as their Desktop browsers.

    I'd like to remind you that every Windows 8 (RT and non-RT) device will also have the Desktop version of IE10. The Flash CV List and the no-plugins policy will not be applied in that browser. Redirection to the plugin-enabled version of IE can be implemented in a single line of code. But how could you have known that? Apparently you never read important things.

    I don't see the point of your last sentence. I'm afraid that I have been using the webkit prefix far too often recently; Microsoft and Mozilla (and to a certain extent Opera) are pushing standards-compliant HTML5 forward more than Google. And don't get me started on the privacy-hole that Chrome is.

    If you want to keep whining, don't do it on this blog. Some people are actually interested in reading useful material.

  32. Stanley says:

    Which failure video for Windows 8 is worse? I can't tell?

    1.) Windows 8 for a System Administrator http://www.youtube.com/watch tl;dr Windows 8 doesn't support multiple monitors thus for any regular office environment where users have 2 or more monitors Windows 8 will only use 1 of them.  Total Epic Fail.

    2.) Windows 8 scares me: http://www.youtube.com/watch yet another video showing how users everywhere are finding major issues with Windows 8.

    Of course Metro and IE 10 is only 1/2 of the problem with Windows 8 but it is a major downgrade from the IE9 browser and important that Microsoft realizes that developers are not happy about Metro, and users hate it even more.

    Welcome to the new Windows Vista 8!

  33. @Stanley says:

    I feel like I have to defend Windows Vista!

    Window Vista was plagued by initial performance issues, bad driver/hardware support and some software bugs. But Vista provided some really good architectural and usability improvements to Windows. Those improvements were refined in Windows 7, which turned out to be a great OS.

    Windows 8, on the other hand, is much worse than Vista. Compared to Vista, Windows 8 is a usability nightmare. It is unintuitive! Bugs can be fixed, but bad UI decisions cannot. I am sure that if Windows 8 was released as a for-touch-only OS, Windows 8 would not have recieved any negative feedback at all. Instead Microsoft will force the OS on every new computer!

  34. @Stanley says:

    Personally, I did not have _ANY_ problems with Vista. And it was thanks to Vista that manufacturers stopped the mass production of sh*tty PCs – it was the version of Windows that stepped up the bar on hardware. And except for the CPU, hardware requirements have been the same in Windows Vista, 7 and 8.

  35. George says:

    I know it's unrelated, but I'd like to ask if anybody else got the BrowserChoice Screen today. I'm running Windows 8 RTM and I think it appeared due to an update, but I don't know how to uninstall it completely. Any ideas?

  36. Arieta says:


    The problem with Vista was the lack of driver support in the early days, including some rather high-profile ones like Nvidia motherboard chipsets, which prevented a whole slew of otherwise completely capable platforms from working at all. And, the RTM had some very nasty bugs, like the one where file transfers went at 1mbyte/sec.

    Once those got fixed by SP1 and driver support improved, Vista was as good as 7, with some tweaks.

  37. Don says:

    Can someone from Microsoft please clarify what is going on with Flash in Windows 8?!

    I'm sick of all the issues that have been brought up without any response from Microsoft – not a single bloody response!

    I will absolutely NOT apply to the whitelist until there is confirmation from Microsoft over the details.  Currently due to the constraints for applying I can't even satisfy the requirements and therefore can not physically apply!

    Of course like most I hope that Microsoft has come to their senses on this and is working hard on rolling back this list as it has caused nothing but trouble and worse yet solved absolutely nothing.

    Please provide us with an update… Only getting the rumors from internal staff (that businesses and enterprises and users alike are unanimously against this list) is comforting but means nothing until a program manager from Internet Explorer steps forward and clears the air.

    — Don Bradley

  38. @Arieta says:

    The biggest complaint I heard about vista was the security confirmation messages, which is a bit silly considering it took 5 seconds to turn off in the control panel.  But that didn't stop everyone I know from saying thats why they hated vista.

  39. Win8 says:

    It's funny to see people still arguing for an IE10 release for Windows 7.

    That won't happen. PERIOD.

  40. @Win8 says:

    If they do not produce an IE10 for Windows 7 there will be lawsuits.

    Quite a few of them actually.

    The promise of an update for IE was part of several strategic descisions to roll out Windows 7 troughout companies for next year.

    We like many already started application update programs for browser based apps from IE8 to IE10 which will roll out in 2013 after the Windows 7 upgrading has completed.

  41. @Win8 says:

    You can say it all you want but it doesn't make it true, their plans haven't changed: the Windows 7 version will come out.

  42. Win8 or the Highway says:


    >Still waiting for non-existant IE10 for Win7


  43. Windows Phone 8 delay says:

    Now that the Windows Phone 8 is delayed because Microsoft didn't get the SDK to developers in time (and they are still waiting!) does this mean that it slipped because developers were busy backporting IE10 (to WindowsPhone and Windows 7?)

    We obviously couldn't care less about Windows Phone because, well, it sucks and no one wants the stigma of owning a windows phone… heck you'd get laughed at in a Starbucks if you actually pulled it out and used it.

    But seriously,… where is the Windows 7 release of IE10? we need to start testing this browser and we can't even start yet!… October is around the corner and we haven't been able to do any testing yet!

    MSFT fanboy trollers note: yes we know there was a preview release we could install on spare hardware (if we had any, which we don't)… but seriously… this is a browser, it should never have been tied to an OS in the first place!  You lost the court case against Netscape and the DOJ told you to quit playing games!

  44. Test says:

    We have found issues on our webpages with the Metro browser of IE10 that do not happen when we use the desktop version of IE10

    How do you test and debug for finding those errors?

  45. Test says:

    Thx, we'll look at that

  46. Harry says:

    Testing Metro IE is/will become a major pain without a proper development tools [F12] feature.

    Using Eric's suggestion to use the desktop browser and shut down ActiveX is a weak attempt at emulation and is far from an accurate representation of Metro IE.

    The first problem (as mentioned on the IE blog DAILY!) is that Microsoft has not provided any JavaScript interface/method/property to determine if the user is stuck in Metro IE or in the fully capable desktop browser.  So developers can't even cater their content to the browser to provide the best experience possible. (Again, Microsoft – Please explain why you are being silent on this and not considering fixing our bug reports!)

    The second problem is that many of the differences have nothing to do with ActiveX.  Certain JavaScript will now fail silently in Metro IE 10 without any explanation or log (since there is no developer tools!!!!!!!!!!! Hint Mother Trucking Hint!!!!!!!!!) so basic functionality like using a synchronous window.prompt() call to get information from the user will completely fail in Metro, yet work as always in Desktop IE.

    The third problem is that many of the test scenarios we are trying to handle are the "handover" scenarios where the user arrives at our site/application using the Metro IE browser and they reach a point (or somehow we determine they are using Metro) and we need to provide the ability for the user to switch to the desktop version… or a better browser like Chrome or Firefox.  The problem in the simplest case (Metro IE to Desktop IE) is that the user's session is completely LOST! so when the user gets prompted (*see next item below*) to switch to the desktop version they are taken from one context to the other but when they load up the page on the desktop, they don't have their session any more and are thus forced to the login page (for apps), or just completely lose their profile information on websites.  If the user is forced to the login page (or needs to re-login) then they do so, but at the COST that they completely lost where they were in the application and have to re-search to find the spot where they were FORCED off.  There's a 2 word phrase for this in Web Development and it is: "Usability Nightmare"!

    The forth problem is that even if we manage to detect that the user is stuck in Metro and we therefore need to switch them to the full desktop experience so they don't suffer from a partial Internet experience… we are still stuck for how to provide a decent message to the user.  The easiest is simply to add an alert that notifies them:

    "Metro Internet Explorer is not compatible with many sites including {AppName} .  In order to use all the features of {AppName} you'll need to switch to Desktop Internet Explorer or use a fully capable Metro browser like Google Chrome or Mozilla Firefox."

    However the next problem is that there is no nice way to link the user to the desktop browser if that's what they choose to use.  Developers then have to bump the users to a special page that has the meta tag on it to force the helper bar to popup so that users can open up the app on their desktop (because inline attempts to inject the meta tag is unreliable).

    The fifth problem is the quasi partial support for flash.  This had been the biggest disaster in terms of statements made by Microsoft on the IE Blog without ANY follow up information about this major change.  I personally cancelled my MSDN subscription last week over this wall of silence and I'm no longer making any attempt to defend Microsoft's/IE's name when talking with fellow developers at work, meetups or conventions.  Microsoft re-build an optimized version of Flash with Adobe to ensure that it worked well with Metro IE then told developers that they would have to jump through hoops, spend a fortune on hardware, give up corporate information, run a barrage of tests, expose their flash code to Microsoft, and finally wait up to 3 FULL MONTHS to ***POTENTIALLY*** get on the special list that censors which sites are allowed to run flash content (regardless of what type/purpose it is for).  I can't stress enough how much of an UNBELIEVABLE KLUSTER FUDGE this was Microsoft.  I'm physically speechless when I even think about where I would start to express my distaste for the actions Microsoft has taken… followed by complete and total silence on the matter.

    The sixth problem is that the Flash URL censoring list never took into consideration that developers are always testing their content locally, or pushing to Intranet servers for their fellow developers, QA technicians, and Management to review.  There is no easy way to make the flash content work locally (and even when pushed to production there is no way to properly test it until your site has gone through the 3 MONTH WAITING PERIOD! (yes their are some registry hacks to get a *SINGLE* internal site to behave properly – but this is far from helpful or intuitive!  Hacking the registry should not be required to test flippin' web pages!!!!!!!)

    The seventh problem is that Microsoft has given up on developers… which in turn has caused developers to give up on Microsoft.  Technology is moving incredibly fast at the moment and with so many platform and browser choices out there there is no room for Microsoft to start playing games with developers.  Telling my customers that they need to upgrade to a better browser because Microsoft is stonewalling and we're not confident in their future developer relations would be a *VERY EASY* statement to make with plenty of backup information… and plenty of alternative browser options for the customers to choose from.

    Finally since testing in Metro is now basically one of the hardest things to do (even on a desktop PC with access to an F12 key!) I fully expect that developers attention to detail for Metro IE will diminish significantly, glitches and bugs will crop up… and there will be one very easy workaround that will for sure become the #1 answer.


    Dear Customer:

    We are aware that there are many issues using {AppName} in Internet Explorer in Windows 8 in the Metro Mode (the one with all the square tiles vs. the traditional full desktop.

    Most of these limitations are within the browser itself and beyond our control.  We highly recommend you use the desktop version of Internet Explorer (or any other browser).

    However if you'd prefer to use a browser in Metro Mode we strongly encourage you to use Google Chrome or Mozilla Firefox as they do not suffer from the same limitations of Metro Internet Explorer.

    Thanks – {EveryCompanyOutThereThatValuesTheirCustomers}


    oh, and I'm sure it goes without saying – please fix your blog comment form! it's insulting enough that you don't listen to developers but you can't even hear what we have to say when your comment form regularly eats our posts unless we remember to save a copy of them first!

  47. @Harry says:

    I'm not sure whether Modern-style Chrome and Firefox will have developer tools… Also, stop using "Metro" – I can't take seriously anybody using that word. "Modern" is only 1 character longer, so I doubt you have trouble remembering it.

    You should redirect users to Desktop IE at the beginning of the session. Immersive IE was designed to be "immersive" and "power efficient".

    I only agree with you about fixing this blog's comment form.

  48. Vince says:

    @"@Harry" – why would we call it "Modern"?! I was creating colored squares in my thick client java applications back in 1995! there's nothing modern about creating a colored rectangle with no styling.

    As for redirecting users at the beginning of a session I agree with you this would be the best point to do so.  However as I'm sure you are aware and @Harry pointed out the problem is that developers have no idea the user is actually trapped in Metro mode (yeah, Metro is also not a good description for Squares).  If developers could tell that users were in Metro then they could redirect users to a full browser experience right away – but until Microsoft provides such a feature the developers are stuck.

    I would hate to do this, but the only alternative I can think of at the moment is to sniff for IE10 (or higher) and attempt to render a flash object/add the meta tag right on the login screen.

    Actually this might not be too bad… if we use flash to cover up the message that says that Metro IE isn't supported and that they have to use the desktop mode then when it fails to load in Metro the message will be visible, but for desktop users of IE10 they won't see the warning message because it will be covered up with the flash content.

    Who knew that Microsoft's Metro Internet Explorer 10 would actually  be _PROMOTING_ use of Adobe Flash… just so that developers can redirect Metro users to use the full/other browsers!

    As for your comment about Metro Chrome and Metro Firefox not having a developer tools… you're missing the point!  Those browsers don't need them because the smart developers at Google and Mozilla didn't cripple their Metro browser just to get a full screen browser!  Only Microsoft failed by trying desperately to make Metro IE on a desktop PC behave like the watered down Metro IE on a tablet or phone.

    At the end of the day both Developers and Users suffer a horrible experience because Microsoft was paranoid about battery life on their new tablets.  The hilarious thing is, if they didn't include desktop windows then the tablets would be fine.  YADFBM – Yet Another Design Fail by Microsoft!

  49. @Vince says:

    How does it encourage use of flash if its only a problem on sites that already have flash?

  50. Nick says:

    The pseudo flash support in Metroh is only part of the problem.

    There's no plugin support at all (which depending on your app might be an issue) but more importantly it affects users because they can't install things like Adblock, bug me not, password vaults or form helpers.

    Then there is broken JavaScript… I only know of the alert(); issue right now but I'm sure there are more.

    I also haven't tested this but I've heard that bookmarklets don't work in Metroh IE this will really suck if this is true.

    Finally has anyone got a screenshot of what Metroh IE's date control looks like? Is it user/touch friendly? We often provide an inline calendar for desktop browsers but skip it for mobile/tablet/touchscreen as they provide a better one natively.  Detecting Metro for this is pretty critical but if the date widget sucks for native Metroh then we'll just supply our own.

    So many questions for Microsoft yet so much silence from their Ivory Tower – I sure hope they are working on improving dev relations because right now it absolutely sucks big time!!!

  51. Armend Mitrovica says:

    ie10 for windows7 to be released 24 September ?

  52. @Vince says:

    "Modern" because that's the name. I don't agree with Apple's so-called "Geniuses", but I don't call them by other names either.

    You could put the header there: a suggestion to switch to the desktop browser will be shown only on Immersive IE 10.

    YOU are missing the point about Modern-style Chrome and Firefox: They aren't full-desktop applications (or else they would have developer tools) and they aren't Immersive apps because they're not entirely chromeless. You can call Immersive IE10 half-baked or whatever, but it's really the pot calling the kettle black.

    @Nick – TPLs are fully working on Immersive IE. Also, everything related to the Modern UI is touch-friendly.

    @Armend Mitrovica – So far no public statement on any date. Where did you read that?


    IMO, the web should be plugin-free: plugins cause the most crashes and some of them are resource-hogs. Effort must be put in pushing HTML5 forward because flash is still in a large part a necessary evil.

  53. gabriel morrow says:


    ppl who use ie10 with dnt enabled will not be honered now

  54. hAl says:

    Apache are making a big mistake.

    People do not wan to be tracked by default.

    Apache is now part of the anti-privacy lobby.

    I wonder how much Google and other advertising companies are paying them…

    Living in the EU I am inclined to send a letter the EU commission to ask them to make it mandatory to obide by the 'Do Not Track' setting which should be on by default.

  55. David says:

    Quote: news.cnet.com/…/apache-web-software-overrides-ie10-do-not-track-setting

    "The only reason DNT exists is to express a non-default option. That's all it does. It does not protect anyone's privacy unless the recipients believe it was set by a real human being, with a real preference for privacy over personalization.

       Microsoft deliberately violates the standard. They made a big deal about announcing that very fact. Microsoft are members of the Tracking Protection working group and are fully informed of these facts. They are fully capable of requesting a change to the standard, but have chosen not to do so. The decision to set DNT by default in IE10 has nothing to do with the user's privacy. Microsoft knows full well that the false signal will be ignored, and thus prevent their own users from having an effective option for DNT even if their users want one. You can figure out why they want that. If you have a problem with it, choose a better browser. "

    EXACTLY!!! Microsoft deliberately violated the specs! Once again showing developers and users that Microsoft thinks that they are above the standards by which the rest of the Internet is built on.

    Way to cause a bunch more trouble Microsoft!  Did you think the Flash Censorship List (FCL) wasn't enough?  Being silent about all these changes and ignoring developers was just too easy for ya? You had to go and cause more trouble!

    Well congratulations you win.  We're officially giving up on Microsoft.  All development efforts from now on will focus on browsers that understand what a spec is.

  56. @David says:

    "Microsoft deliberately violates the standard."

    Firstly, shame on those that are involved in the standard for bowing to the advertisers and not making our privacy having priority number one.

    Secondly Microsoft has made it a installation choice. That could wel be in the realm of the spec. It might be a wide interpretation of an opt-in but is aty least an interpretation that respect their customers privacy.

    Apache now looks to be deep in the pocket of the anti-privacy lobby headed by the biggest privacy violator of them all, Google.

  57. Yannick says:

    @Daved – Then tell me, in wich way Microsoft doesn't follow the standard. DNT doesn't have a standard-setting. The only thing is that is have to be the chose of the user. Installing Windows 8 or creating a new account, you can see "Turn Do Not Track on in Internet Explorer", so IE give an announcment of the feature and it's then te chose of the user. The other browser doesn't so actually, they're not following the standard.

  58. Stanley says:

    @Yannick what is the default for that setting when using IE for the first time? – if the user did not explicitly turn it on themselves then it was NOT a user specified setting – period.

    You can be a Microsoft FanBoy all you want but you can't argue against cold hard facts!


  59. George says:

    @David – Like Yannick said, when you install Windows 8, right before you go for the first run, the setup presents you with the Personalization settings: you can either choose "Express settings" (with a brief description of the pre-configured value of each setting) or tweak the system. If you chose Express settings, you are merely accepting that among others, DNT=1 is your choice. In fact, it's a very good thing that DNT is enabled in the initial state: the overwhelming majority of users prefers it that way. If you want to be tracked, you can easily set it to "OFF".

    It's not Microsoft's fault that Apache will brutally ignore it. @David makes a good point with his last sentence; I strongly suspect that Apache is doing this due to pressure from advertisers, of which the biggest is Google The Privacy Hole; Google also wants to push forward it's non-DNT-enabled browser forward. I feel sorry for Apache: it used to be user-focused once upon a time.

    @Stanley – We can say the same: If the user did not explicitly turn it off, then it was NOT a user-specified setting. Apache can't know that and should not hypothesize in any occasion. Funny how you're falling for your own tricks.


    Also, posting the same hate-sh*t under different names doesn't count when you say that most developers agree with you. Stop spamming this blog. I seriously request a flag-for-spam in order to keep vandals like you from annoying interested readers.

  60. Neuro says:

    @George let's be realistic here for a while. The ad companies don't have to follow the flag, there is no legal reason nor a social pressure (and it's not going to be when the majority of internet users doesn't have a clue what we're talking about). They agree to honour it, because they expect that most users won't ever touch the settings. So they can sacrifice the tracking for the few people with a clue, and look like a good guys. Enabling the flag by default upsets the balance, and so they'll most likely ignore it. Yes. they'll be bad now and we'll point at them but so what – it's not like there's any reputation to ruin anyway.

    It's the same situation with adblockers. Most ad providers don't do anything nasty around it, because it's not worth the effort. If IE10 came with active adblocker preinstalled, there would be a war.

    BTW there's a dozen IE defenders who are either the same person, or have memorized the marketing materials perfectly. Do you think there won't be a bunch of IE critics who'll have a similar opinion? Our site is using Flash at one place only and that will be soon gone; nonetheless I think what Microsoft did is ridiculous, and the way they treat web developers (including the poor guys who went to Silverlight – I am glad I gave up on it) for the last year or so rather disgusting.

  61. @Neuro says:

    There is no legal reason 'yet' to follow the flag.

    But lawmakers are taking notice and starting to protect their civilians privacy

    For instance in the Netherlands trackie cookies without explicit consent are already forbidden even when no flag is present in the header.

    If large adcompanies like Google choose to ingnore the privacy setting of their customers they will quickly be under scrutiny from the privacy autorities. Especially in the EU it is likely that ad companies will be forced to follow the privacy settings set by internet users.

Comments are closed.

Skip to main content