HTML5 for Applications: The Fourth IE10 Platform Preview

An updated platform preview of IE10 for the Windows Developer Preview is now available for download. This IE10 preview adds even more support for HTML5 technologies, enabling richer Web applications with significantly improved performance. IE10’s hardware acceleration of technologies like SVG, CSS3 transforms and animations delivers faster rendering than other browsers, as highlighted in this short video.

See some of the new HTML5 capabilities, performance improvements in IE10.

With this fourth Platform Preview, developers can start working with more site-ready HTML5 technologies. You can read the full list here in the IE10 developer guide. Here are a few highlights:

  • Cross-Origin Resource Sharing (CORS) for safe use of XMLHttpRequest across domains.
  • File API Writer support for blobBuilder allowing manipulation of large binary objects in script in the browser.
  • Support for JavaScript typed arrays for efficient storage and manipulation of typed data.
  • CSS user-select property to control how end-users select elements in a Web page or application.
  • Support for HTML5 video text captioning, including time-code, placement, and captioning file formats.

These foundational capabilities are what developers building native applications depend on: working with binary data and files, controlling selection and hit testing in application UI, and providing accessible video content with captioning. The features in this platform preview are available to Web pages now, and will be available to Metro style applications in Windows 8.

Building HTML5 Applications

This IE10 preview supports CORS (cross origin resource sharing) to allow developers to use XMLHttpRequest to safely request, share, and move data across applications on different domains. This is a common pattern developers use to bring data and services together from different applications. In this test drive demo, you can see how CORS is used along with XMLHttpRequest, the File API, and HTML5 progress control to deliver a smooth experience for uploading multiple files to a service on another domain.

Screen shot of IE Test Drive demo Cross-Site Update showing four image files being uploaded in response to a file drop on an HTML5 target element.

Click here to see CORS used with XMLHttpRequest to upload files across domains.

Having the ability to work with binary data and files enables developers to build new kinds of applications and experiences on the Web. This IE10 preview supports blobBuilder from File API: Writer for working with large binary objects (blobs) and JavaScript typed arrays. In this test drive demo, you can see how different file types, including file types which are not natively supported in the browser like PCX files can be read, rendered, and even have their internal contents displayed.

Screen shot of IE Test Drive demo Binary File Inspector showing a hex dump of a PCX file and a rendering of that file using HTML5 canvas and JavaScript.

Click here to see how JavaScript typed arrays used with File APIs to read and view binary files.

As developers build more sophisticated applications on the Web, they have more need for precise control over how end-users select parts of the page. With CSS user select support in IE10, developers can specify which elements in their page can be selected by the consumer when using their applications. In this this test drive demo, you can see how selection control is applied in a sample blog application using the user-select property in a CSS rule.

Screen shot of IE Test Drive demo User-Select showing the markup needed to restrict text selection to a portion of the Web page.

Click here to try CSS user-select to control end-user Web page selection.

Improving Same Markup for HTML5

We continue to contribute to the test suites under development at the HTML5 standards bodies, submitting 118 new tests to them, to further the goal of interoperability and same markup. You can view them at the IE Test Center as well. We strongly encourage all developers to write for HTML5 standards first by always using the HTML5 doc type <!DOCTYPE html> in your pages.

IE10 Preview 4 introduces an updated quirks mode that is more consistent and interoperable with the way quirks modes works in other browsers like Firefox, Chrome, Safari, and Opera. This updated quirks mode supports quirks for page layout, while allowing use of more up-to-date standards features like HTML5 elements for audio, video, canvas, and more.

You can find a full list of new functionality available to developers in the IE10 developer guide here. Download the Windows 8 developer preview to try this update to IE10. We look forward to continued engagement with the developer community and your feedback on Connect.

—Rob Mauceri, Group Program Manager, Internet Explorer

Comments (86)
  1. Erik says:

    Yay! cool perf in the video… why isn't it first??

  2. hart says:

    Windows 7?

  3. David says:

    No Win7 support is a deal breaker for me… too bad, because there's a lot of cool stuff going on here.

  4. Raynos says:

    Can we have browsers working on more then operation system please. Thank you.

  5. Brian says:

    I don't understand the lack of a Win7 release. Is one coming? If not, is IE10 going to be Win8 only?

  6. Jon says:

    You can get the Windows 7 preview at the usual place…/Default.html

  7. piro says:

    Windows 7 release please!

  8. Shelley says:

    Astonished, completely, that you're not supporting Windows 7.

    Seriously, whose brain dead idea was this?

  9. Shelley says:

    Jon, it doesn't work with Windows 7.

  10. sam i am says:

    The lack of a win 7 (or Vista for that matter) build makes this useless for testing of our web apps. Please make a standalone version available for at least Win 7.

  11. ieblog says:

    We will release an IE10 Beta and Release Candidate on Windows 7 prior to IE10’s general availability.

    Web developers interested in working with the new features of IE10 are encouraged to download the Windows 8 Developer Preview at…/home.

  12. Alfonso says:

    Software companies that are interested in developers to test their products are encouraged to make them available in the OS that are used on a daily base, not a pre-alpha OS that can't be used.

  13. Alfonso says:

    And by the way, supporting file upload by passing the file object to a XHR is something that can't be detected, so any decent script is using FormData, but you wisely have chosen to not implement it for IE10, so the end result is that IE10 users won't get the benefit of upload progress because it will fail the basic "if (typeof FormData != "undefined)" test

  14. Arieta says:

    This is absurd. How do you plan on getting people to switch for IE10 when you effectively lock out your entire userbase, and alienate any and all developers who would still support you? The entire point of the platform preview program was to make the development of IE more transparent, but by locking new previews to a OS barely in beta state, you are pretty much killing the entire point. Why release these previews to begin with, then, when it can only be used by an extremely small share of users?

    I can understand the need for pushing new systems, but web developers will not install an entire new test OS just to see how our website may look in a browser with a usage share in complete free fall. You are just making the problem worse, and encouraging what few users you have to switch to another platform altogether. If even previewing code in a new IE version is deliberately made so difficult, then why should the web developers even bother anymore? You guys are leaking usage share all over the place and now you are shooting yourself in the foot to top it off.

    I was looking forward for checking that updated Quirks mode (a much needed addition!). But I guess I won't be able to, until IE10 final is released. Because I'm convinced now that Windows 7 will not even see a beta version of this browser either, and the final release will be a dumbed-down pale shadow with no support.

  15. Arieta says:

    …. oddly enough, I've attempted to post that message 4 times in IE9 and all of them failed, yet with Chrome it was sent on the first try. Not even the "thanks for your comment" box appeared in IE9. This is fast becoming a comedy.

  16. Charles C says:

    If Win7 IE10 is planned, will the new windows 8 http.sys which supports WebSocket also be made available for IE10 on Win7?


  17. Confused says:

    It would have made sense to me to release this for Win 8 Developer Preview only if the installer actually replaced PPV 3 on the Win 8 Developer Preview, but it doesn't.  All it does is install a different build in a different folder and give you a desktop icon just like PPV 2 id on Windows 7.

  18. Martin de Keijzer says:

    Never thought I'd say this, but this is looking alright! Now for that WebGL support…… 😉 Sorry the past keeps haunting, delivery of many types of techniques needs to be high to regain a user like me. But I'm optimistic after seeing this!

  19. html5 advocate says:

    After huge jumps from IE 9 and between each PPV of IE 10, there does not appear to be any improvement in HTML 5 suite scores here from PPV 3.

  20. CSS guy says:

    What about the CSS3 border-image?

  21. Eduardo Valencia says:

    "We will release an IE10 Beta and Release Candidate on Windows 7 prior to IE10’s general availability.

    Web developers interested in working with the new features of IE10 are encouraged to download the Windows 8 Developer Preview at…/home.


    Are you kidding, Internet Explorer 10 is far from release,we will have to wait at least 6 more months to see a bits of the browser?

    This is ridicoulous

  22. Lance says:

    Ha, just when I was warming up to making IE more of a part of core development instead of as a check for what shims need to make it work in each variation of IE's quirks, you guys start making testing where the platform is going a pain, o well it is just easier for IE to remain dead to me.

  23. Alfonso says:

    We should all start a #boycottIE10 until they provide a test version for Vista and W7 (that can be installed besides IE9). No testing of IE10,  no reporting of bugs,  no adjustments for the new features, nothing at all until they provide a version for vista and 7.

  24. what says:

    Where is Windows 7 version???? This time with the outdated OS trick won't work!!!!

  25. sam i am says:

    While I know that you have plans to support The IE10 previews on Win 7, I question the lack of support now. As I see it there are 3 reasons for these previews:

    1) Allow developers to start testing legacy web apps with IE10

    2) allow developers to start testing various enhancements that would allow IE and other browsers to share common HTML/JS

    3) Allow developers to provide feedback to allow a more stable and accepted final version of IE10

    4) Return developer interest back to IE

    None of these 4 are really being properly addressed by allowing a Win 8 only version since you probably cut down the number of developers using it by %90. Out of the 4 reasons above, I believe that #4 is the most important to Microsoft. With the vast majority of developers using Chrome and Firefox, most developers only use IE to test that their sites properly render in IE10. The earlier developer previews started the process of reawakening developer interest in IE10. Limiting this to Win 8 for the sake of interesting developers in Win 8 at the same time will likely backfire. It is a lot easier to deploy IE10 preview than installing a full OS. I am sure that there are technical reasons that make releasing the Win 8 version the easy route for you now (leveraging APIs currently only in Win 8, or other reasons), but keeping developer interest in IE10 is probably well worth the effort to make a Win 7 version available.

  26. KS says:

    @ieblog: in other words, you will not catch some of the bugs in IE10 that happen only on Windows 7 because no one tests it one Windows 7. What a concept. You have been trying to not repeat your old mistakes. But that doesn't help if you make new mistakes with eyes wide open. Please reconsider.

  27. Craig says:


    Great work on IE10 so far.

    IE9 was such an improvement that after many years I finally switched back from other browsers.

    I am really looking forward to the complete release of IE10.

    However, would you please dedicate an upcoming post to explain the supported platforms?

    There is a lot of confusion over what will and will not be supported.

    I think that this would ease a lot of people's minds.


  28. Olivier says:

    We need IE9 and IE10 on Windows XP. Microsoft, you know XP is not dead and won't be dead for a long time. I know many people who switch back to XP after very bad experiences with 7.

    And I want to use IE because others browsers aren't that good. Looks like a lot of people are stuck with IE8 for a long time… :-/

  29. sam i am says:


    XP support is not going to happen and that is a good thing.

  30. Sharon [MSFT] says:

    @Alfonso, FormData is supported in IE10.

  31. 4esn0k says:

    is XHR-streaming supported?

    ('onprogress' in (new XMLHttpRequest()) ?

    I need Windows 7 =) to test it myself…

  32. Eli Mitchell says:

    No auto-update yet? C'mon IE, you *desperately* need it ASAP!

  33. Klimax says:

    @Eli Mitchell:

    ignoring Windows Update?(which is more or less autoupdate for Windows and MS programs)

    (Anyway forced auto-updated will most probably never happen – too many legal problems and would go against stated goals. And that's good thing. I never recommend FF or Chrome due to that insanity)

  34. Yuhong Bao says:

    Which standards mode is IE10's interoperable quirks mode most similar to and what are the exact differences?

  35. phil says:

    Now, the chrome performance comparision for seattle rain is not fair, because latest chromium has gpu composition for everything, so there it runs at 60 fps. I wonder what makes the difference from IE10 PP4 to PP3, where fps is really low, thought they already have full gpu acceleration in IE9?

  36. Jack Deed says:

    The video doesn't work in Firefox. It's unfortunate that this blog doesn't demonstrate HTML5 video best practice. See for some pointers.

  37. Pebe says:

    Will the new quirks mode be available everywhere or will the old quirks mode become active somewhere for compatibility reasons?

  38. Andrew says:


    It works just fine on my FireFox 8, Chrome 5.0.5, IE 8 and IE 9.

    Seems quite interoperable.

    Looks like the problem is on your side.

  39. @Pebe New IE10 has two quirks modes, IE5 quirks and Quirks.

  40. phi2x says:

    Typed Arrays is the first stepping stone towards WebGL support in IE 10. That gives us all some hope 😀

    I can't wait for the next developer preview 😉

  41. hAl says:


    Windows 8 cannot be installed on my laptop thathas windows 7 on it. The installation fails

    Are you suggesting I need to buy new hardware to test IE10?

  42. phil says:

    @phi2x Hopefully we don't get WebGL but something that fits more the js world not some hardcore c-style apis.

  43. Andrey says:

    On User-Select demo selection "Turn off selection everywhere" also prevents input characters into "Name" and "Comment" text areas. Is it suppose to be? Why?

  44. Daniel says:

    I don't get it. Why do you hate web developers so much?

    We want to test IE10 Previews on Windows 7, the OS we work on doing our everyday jobs.

    > Web developers interested in working with the new features of IE10 are encouraged to download the Windows 8 Developer Preview …


    > Note: The .iso file that contains the developer tools requires a large capacity DVD called a DVD-9, as well as a DVD burner that can handle dual-layer (DL) DVDs. Most modern burners should be able to handle this format.

    Ouch. Not available on any of our 5,000 Computers.

    > We will release an IE10 Beta and Release Candidate on Windows 7 prior to IE10’s general availability.

    Yeah right. That leaves us with many small and annoying issues that can't be fixed because they were reported too late to get properly fixed.

    After the first and second Preview I got a really great impression. Completely busted.

    Miscroft simply hates the web, web developers and anything that is related to the web.

  45. Steve says:

    Is it just me, or do the "whiners" (about Win 7) not know that Win 8 is going to be just as big a difference, if not bigger than Win 3.1 to Win 95? I'm still on Vista and see no reason to go to 7. I'm jumping over it and going to 8 when it comes out.

  46. Alec says:

    The lack of support for Windows 7 decreases the number of users willing to beta-test IE10. This means you will have fewer beta testers and will receive fewer bug reports. Not a wise decision, IE team. Marketing should never trump beta testing.

  47. ieblog says:

    @Pebe: The new quirks mode will be the default for all pages without a <!DOCTYPE> directive. IE’s legacy quirks mode (a.k.a., IE5 mode) will continue to be used in Compatibility View. Pages can also opt-in to legacy quirks mode by using a meta tag: <meta http-equiv="x-ua-compatible" content="IE=5" />.

    IE uses Compatibility View when the user presses the compatibility view (broken page) icon, or when the options labeled “Display intranet sites in Compatibility View” or “Display all websites in Compatibility View” in the Compatibility View Settings dialog are on. “Display intranet sites in Compatibility View” is on by default.

  48. Alfonso says:

    @Sharon [MSFT]

    I would like a clarification about FormData.

    The ticket at Connect requesting it was closed as won't fix, but now you're stating that it's supported.

    FormData isn't just about passing a File to XHR, it allows to send a whole form as well as specifying the name of the parameters.

    I promise that I'll test it when you provide a version for Windows 7, but meanwhile I have to believe the fact that the ticket was closed with WONTFIX

  49. Jack Deed says:

    @Andrew: "It works just fine on my FireFox 8, Chrome 5.0.5, IE 8 and IE 9. Seems quite interoperable. Looks like the problem is on your side."

    No, the problem is their side. You're using Flash video in most of those cases. I'm talking about HTML5 video. It's amusing that a blog post about HTML5 features doesn't feature interoperable HTML5 video. It makes Microsoft look like they don't know what they're doing. Quite unprofessional.

  50. s says:


    please test this feature on the low speed internet.

  51. Josh the Nerd says:

    @Alec: IE10 has not entered beta-testing yet. The platfrom previews are only for developers to test their own website code with the new platform. As ieblog clarified in a comment, the beta will be available for Windows 7.

  52. gdalsnes says:

    Microsoft must be the worst software company on the planet to support "old" Windows versions.

  53. Real McCoy says:

    Can anyone verify the tests on…/submission layed by Apple, Google and Microsoft? Last time when I checked this test:…/paused_true_during_pause.html, it passes but the video was still running after the page loads as opposed to its intended behavior (stay paused).

    Link to Connect issue:…/html5-video-doesnt-persist-the-paused-state

  54. Klimax says:

    @arghhhhhhhhhhh 30 Nov 2011 6:02:

    Really? Hm,then I guess you could show company supporting old OS which has age +10 years, which is general consumer and corporate platform or OS which is at +5 years.

    I am pretty sure there is no such company and it doesn't make that much sense either. (even 6 years in PC world is long…)

  55. Vasil Dinkov says:

    Since this is what bothers me at the moment, I am going to comment just about it – the current implementation of the new touch events seems to be pretty different from what all other dominant mobile browsers currently do. And I am not talking about the syntax (though it would have been great if you went with the existing W3C touch events model) or the way you handle multi-touch (i.e. by firing separate events for each touch point), I am talking about differences in which events are fired when. Why don't you just follow WebKit/Opera Mobile and fire the MSPointer* events and the old mouse events (for compatibility with existing web sites) exactly how they do it? IMHO the best possible thing to do is to follow their established model instead of creating a new one which is quite similar but not completely the same.

    Just some quick examples from my brief tests (these are related to the mouse events fired by touch input since this is what I tested for now):

    1) you fire mousemove, before mouseover when you hover/tap some element

    2) if you tap over an element and start moving the finger, you fire mouseover/mousemove events on touch start – in other browsers no mouse events are fired at all if you move the finger

    3) the same goes for if you touch outside the element, move the finger over it and release

    I guess you'd agree 1) is definitely an issue.

    As for 2) and 3) I must admit to some extent this probably makes more sense than what other browsers do since you could apply hover styles and possibly make some existing scripts (like tooltips, etc.) quite "work" without firing a click on the target element but this is completely incompatible behavior with browsers supporting the W3C touch events and it will surely cause headaches to web devs in certain cases.


  56. Andy Earnshaw says:

    I *was* actively participating in reporting issues with the Internet Explorer previews, but since Windows Virtual PC won't let me install Windows 8, then I'm afraid I can't download this latest preview.  I did try VMWare Workstation, but I'm not happy with having to install so many things solely for the purpose of testing IE 10, so I removed it when my trial expired.

    I can't understand this.  The point of the developer previews is so that new features can be tested and issues can be found early on, why are you restricting the number of people that can install IE 10 PP 3 & 4 by tacking on the requirement of an entire operating system?  Clearly, you don't value developer feedback as much as you indicated in the earlier previews.

  57. odo says:

    Just add a setting that allows one to automatically open all tabs of the last session on starting. html5 is important and yay to you all for improving the browser so far so fast but little convenience options like this (and a decent addon-system – manuall adding a standard search engine, mouse gestures, search previews) are the only reasons i am still sticking with firefox instead of ie.

  58. Nathan says:

    Your comment submission is SEVERELY BROKEN!!!!! (this is like attempt number 10 to submit)

  59. Nathan says:

    Utterly futile blogging system Microsoft – I'd suggest you get off Community sever and get on a real blogging platform!

    Since my last 20 attempts to post my comments from 3 different browsers have all seemed to fail I've had to resort to tools that actually work!

    Here is my comment:

    I had to use pastebin because this blog software sucks so badly Ughhhhh!

  60. Vasil Dinkov says:

    OK, I think I am becoming more and more pessimistic about the whole MSPointer* concept. You should agree that the following statement:

    "Rather than requiring you to create code that handles each type of input separately, Internet Explorer 10 introduces the concept of a pointer."

    posted here:…/hh673557(v=VS.85).aspx

    is so overly exaggerated that it's almost complete hoax. I mean, apart from simple apps like the demo draw application you posted, in reality developers will still need to tweak many aspects of their apps based on the input method as the behavior of the mouse cursor (and the events fired) cannot really be compared to those of a finger or a stylus although there are touching point, of course.

    So in the end, I am starting to think the W3C touch events model in reality is much simpler to chew and use by developers. So why not at least add support for it too and allow IE10 to behave like all other dominant mobile browsers out of the box?

  61. Andrei says:

    @Jack Deed: IE uses H264 for the video in HTML5 while Opera and Firefox use webm. So Flash is really the only "interoperable" way.

  62. Please IE10/Win7 says:

    I'm afraid that although the same engine is used, IE10 won't be tested as well when there's not a Win7 release. Win7 has a much bigger audience (willing to test). But hey it's YOUR product.

  63. sleeper says:

    No Win7, eh? "Go get an alpha release of Win8 OS", you say? "HELL NO!" Says I. FLAME ON! This is why so many developers have left you. What happened to "Developers, Developers, Developers!" Seems one has to read the fine print. No Win7 support? Then who cares whats in IE10. IE has been the the worst thing to happen to the Internet since it's inception. DIE NOW!!!

  64. Harvey says:

    @Jack Deed – Unfortunately Microsoft botched HTML5 for the rest of the Internet by not natively by default supporting a non DRM-Encumberd encoding/format for HTML5Video and HTML5Audio.

    Congrats IE on continuing to be the "Boat Anchor" of the Internet – even with all these massive improvements… it takes a special kind of EPIC FAIL to take 10 steps forward while taking 13 steps back

  65. Arieta says:

    Is there a list for what exactly is updated in the IE10 quirks mode? Is it the same as the old quirks mode just with <audio> and <video>, or can we use things like updated javascript and css2/3 as well?

  66. Tanya says:

    I know browser sniffing is bad and all that jazz but I can't download Win8/IE10 yet and I wanted to know what kind of info is returned by this:


    document.write('userAgent: ' + navigator.userAgent);



    document.write('appName: ' + navigator.appName);



    document.write('appVersion: ' + navigator.appVersion);


    If someone can save that to a file and test it out (and report back here (pretty please!) I would be forever grateful.

    In particular I'm curious what kind of spaghetti is returned by the appVersion property 😉

  67. Alfonso says:


    Why do you care about quirks mode?

    Just add a <!doctype html> to you page and make it render the same way in all the browsers without having to look back.

  68. Klimax says:

    @Harvey 1 Dec 2011 9:01 AM:

    H264 has no concept of DRM, that is added by platforms.

    Webm may or may not have patents – it is currently not known. (search however is ongoing)

    And because there is no patent protection from Google – current owner of Webm – big companies can't take risk as they would be primary target of patent owners and trolls. (known also as patent submarines)

    Anyway H264 is more efficent without loosing quality or size.

  69. Sharon [MSFT] says:

    @Alfonso – I'll have to look into the connect bug resolution. In the meantime, FormData documentation is here…/hh453198(v=VS.85).aspx

    @4esn0k – xhr progress events are supported in IE10, the new Cross Site Upload demo on the ietestdrive is using them as well as other features.…/CORSUpload

    @Andrey – user select shouldn't block you from entering input. Let me know if you have repro steps. I don't see that same behavior.

  70. Dave says:

    @Klimax – you've obviously been out of the web dev thing for a while.

    It has already been determined with full explanations and details that h.264 (although a good video format) is a terrible choice for the open web and can not under its current state be used x-browser, and x-platform, and x-device as the HTML5 Video format of choice.

    Suggesting we use h.264 is like kicking a dead horse.  We've discussed this ad nausium and the upshot has always been the same.

     h.264 is DEAD on the WEB.

    Now if you think you can convince the powers that be to fully open the format, codec and remove the licence pools and return the money to those vendors that got suckered into paying, by all means go for it – many have tried.  The reality is that companies like Microsoft got suckered in early and have lost too much money to realize its time to back a new horse.

    Quite sad really, because it is the World Web Web and all the users on it that suffers in the long run.

  71. Alfonso says:

    @ Sharon [MSFT]

    Thank you very much for the reply and for correcting the status of the bug

  72. Xero says:

    Can anyone test the result of this test on new platform-preview and post the result here:…/Hixie_DOM.html

    Compared to Safari, FF and Chrome, IE9 and 10pp2 perform hideously.

  73. Arieta says:

    @ Alfonso:

    Exactly for the same reason they are updating it. Not all sites use a doctype and expect it to work in the real world. Not all site CAN do that, without a substantial rewrite to fix their broken (but decade-long functional) code: in these cases, IE is the only browser to not display the site correctly, with <video> on top of it.

    As for me specifically, I'm wondering if new javascript + css is allowed, because I'm writing my own userscript for a site that runs without a doctype (and the site owner has no intention for updating).

    With that in mind, I'd prefer if we had built-in usercript and userstyle support in IE10 – custom CSS support is already there since IE5, it just has to be split up to work with per-site rules. And, a forward compatibility list that works like the current "broken page" compatibility view, just the other way around: instead of locking users in older modes, it allows users to lock into newer rendering modes (and keep viewing the page in that mode on subsequent revisits).

  74. Klimax says:

    @Dave 1 Dec 2011 3:13 PM:

    Can't be dead if other choices are not still cleared – companies can't implement them as they would be at huge risk of lawsuits. There were already cases of patent submarines – this would be another rich target. Remember, better to deal with known then unknown and since Google doesn't offer patent indemnification, you take the risk as implementer.

    That's the problem: there is way too many software patents to be sure somebody doesn't wait for you. (And defending is quite expesnive)

    BTW:There is codec for webm which IE can use, so IE users can view both videos…

    TL:DR version: Patents are everywhere and just saying so doesn't make them go away. (See Smartphones patent wars) And submarines like targets like Microsoft or Apple. (And this whole mess needs fixing)

    Note:I left aside technical matter/differencies as it is insignificant until patent situation is cleared.

  75. Michael Herndon says:

    Has there been any work on the paged media queries for printing purposes?  

    The paged media module would be essential for anyone building new reporting using CSS3 & HTML5. LOB applications would greatly benefit from this.  

  76. steve_web says:

    @Klimax, @Dave, @Microsoft

    I understand that the whole patents, lawsuits, royalties, etc. stuff are complicated regarding video formats/encoding etc. however at the end of the day we are stuck with the same scenario – which format can we use for video across all browsers, that is open just like the rest of the web.

    As you can see from Wikipedia:…/HTML5_video

    The problem is in the "Browser Support" table… there is not a single vertical column that is entirely green – thus there isn't a format I can use today that will work natively without user intervention across all modern browsers.

    Admittedly, the best option thus far is VP8(WebM) as at least it is __*possible*__ across all browsers.  I just wish that Microsoft (and Apple) would hurry up and support WebM natively so that developers can actually use HTML5Video (something we can't currently).

    Based on the fact that IE/Safari __*can*__ enable WebM video it seems absurd that they (Microsoft/Apple) are holding back the Web by not supporting it natively.

    It just sucks that Web Developers pay the price here by not being able to provide simple content to their users – thus we all lose.

    omg! this blog commenting system is still brutally busted I see – can we get an ETA on a fix for it? (surely no one has a patent on successfully submitting a form!)

  77. Xero says:

    @steve_web, there is a timeout after which the comment form expires the session of non-account holders. If you have Windows Live ID you can log in and you will never encounter the issue as there is no timeout/session-expiry for the logged used.

    But I agree with you, this issue requires attention. One way to fix could be;

    – Remove timeout for unlogged users.

    – Provide captcha or IP-based observer to prevent the spamming. Something like:

      IF sender is unlogged

      AND senderIP is resubmitting the duplicate comment

      OR senderIP is resubmitting the comment in less than 3 minutes

      THEN reject the comment.

  78. JAB Creations says:

    Preview 4 crashes constantly on my site and the report issue option doesn't accept my credentials even though I just signed in to my email account with the exact same credentials. Not sure why I'm bothering to even post since Microsoft has trolls who attack (now former) customers such as myself instead of listening to people like me who would have otherwise endorsed your products and services if your management DID actually consider what we are saying. We'll see if this post even shows up on the blog though I doubt it.

  79. Ranjeet Bassi says:

    For people who are tryng to install The fourth preview of IE10, it is presently available for Windows 8 developers preview.  What Microsoft wants to do , is to ENCOURAGE web developer, software developers to develop applications for the new gen windows , which by the way will be revolutionary. If you do have personal problems with IE9 or IE10, please do move on and try out other browsers.  In my own prespective, I see IE10 a great browser to use in windows 8. I have  installed windows 8 developer preview, and i have to say that  IE10 will quickly change the way how the web works. I highly recommend anyone who is trying to install windows 8 dev. preview, to partition your hard drive so that you could install windows 8 dev. preview.

  80. I don’t see any issues with the preview of IE10 not running on windows 7, I would always install a preview of IE on a virtual machine, and this virtual machine can just as well be Windows 8 then Windows 7.

    The concept of people wishing to directly install a preview of IE10 on their current machine makes me think they just don’t understand risk control.

  81. DT says:

    Unless something has changed or I'm misremembering things, the platform previews install as standalone alongside existing IE installs, not over the top of them, so what risks are you referring to?

  82. Mark Feetham [MSFT] says:

    @JAB Creations. We've checked the report issue option and not able to reproduce the fault you describe. If you want to file the crash problem via instead, we can investigate.

  83. Tim says:

    Considering all of the comments about how difficult it is to post I wanted to try.

    This is my first attempt using Chrome.

  84. Tim says:

    Wow. That was EASY.

  85. SeanJenkin says:

    Re: Comments on the Blogs Comment system. We have been listening and I realize it's taken a very long time, but today we've rolled out another set of fixes around the comments issues you have been reporting. Hopefully you've seen a lack of duplicate comments the past few weeks. Today we've pushed out bits to fix the submission of the comments along with the time comments can take to load.

    If you still see issues, please use the comment form here ( and report them to me. I'm not watching every IE blog to know when you note issues so please help yourself by getting the feedback to the correct place. 🙂


  86. snarkmaiden says:

    Testing the updated commenting system by pointing out that IE9 supports WebM if you have the codec installed; whether a content owner chooses to encode in WebM is a different matter…

Comments are closed.

Skip to main content