Windows Release Preview: The Sixth IE10 Platform Preview

Article
05/31/2012

With IE10 in Windows 8, we reimagined the browser. We designed and built IE10 to be the best way to experience the full Web on Windows. Consumers can now enjoy more touch-friendly, fast and fluid Web applications with the updated IE10 engine included in the Windows Release Preview. This sixth Platform Preview of IE10 delivers improved performance and support for touch-first HTML5, as well as a new power-optimized, touch-friendly Adobe Flash Player that enables content on compatible Web sites to play in the Metro style Web browser. IE10 also sends the “Do Not Track” signal to Web sites by default to help consumers protect their privacy.

This video shows some of the performance and touch improvements in the sixth IE10 Platform Preview, part of the Windows Release Preview.
(This video is also available on Channel 9)

You can read more about the improvements to the Metro style browsing experience on the Building Windows 8 blog. The remainder of this post discusses the underlying HTML5 engine.

Windows 8 includes one HTML5 browsing engine that powers both browsing experiences (the Metro style one and desktop one) as well as Metro style applications that use HTML5 and JavaScript. The common HTML5 engine provides consistently fast, safe, and powerful support for Web standards and the Web programming model, for both browser experiences as well as for Metro style applications.

Consumers experience this power with responsive, touch-friendly pages that safely take full advantage of the underlying hardware. Some examples that you can try at the IE Test Drive site with the Consumer Preview include the Chalkboard Benchmark for common touch actions like panning and zooming and a multi-touch capable Web page for manipulating photos and images. You can read the full list in the IE10 developer guide.

Touch-friendly Adobe Flash in Metro style Internet Explorer 10

The Windows 8 Release Preview includes a new power-optimized, touch-friendly Adobe Flash Player. Adobe Flash content on compatible Web sites will now play in Metro style IE10. Metro style IE10 with Flash on Windows 8 enables people to see more of the Web working with high quality, especially compared with the experience in other touch-first or tablet experiences.

We believe that having more sites “just work” in the Metro style browser improves the experience for consumers and businesses alike. As a practical matter, the primary device you walk around with should play the Web content on sites you rely on. Otherwise, the device is just a companion to a PC. Because some popular Web sites require Adobe Flash and do not offer HTML5 alternatives, Adobe and Microsoft worked together closely to deliver a Flash Player suitable for the Metro style experience.

Both IE10 on the Windows desktop and Metro style IE use the same integrated Flash Player, with no need to download or install an additional player. IE10 on the desktop provides the same full Flash support as previous versions of IE that relied on the Flash Player plug-in, and continues to support other plug-ins. The Metro style browser continues to provide no support for other separate ActiveX controls or plug-ins.

While any site can play Flash content in IE10 on the Windows desktop, only sites that are on the Compatibility View (CV) list can play Flash content within Metro style IE. We place sites with Flash content on the CV list if doing so delivers the best user experience in Metro style IE with those sites. For example, how responsive is the content to touch? Does it work well with the onscreen keyboard, or affect battery life? Do visual prompts comply with the Metro style user experience guidelines? Sites that rely on capabilities (e.g. rollovers and P2P functionality) that are not supported within the Metro style experience, and don’t degrade gracefully in their absence, are better off running in IE with Flash on the desktop. Site developers continue to control the content they serve to browsers. Developers can send HTML5 content to Metro style IE, or express their preference that Metro style IE prompt users to run their site on the desktop (see details here).

A good Flash Player experience is part of a no compromise experience across all form factors of PCs, including touch-centric PCs running Windows 8. We’ve heard feedback from customers about their experience with sites that do not offer an HTML5 experience. For example, try pbskids.org on an iPad. Some workforce solutions, like Beeline, require Flash. Some financial management sites, like this one, require Flash. And some sites still deliver their best experience with Flash, such as youtube.com.

Adobe and Microsoft added support for touch gestures – like double tap and pinch to zoom – that work consistently across HTML5 and Flash. Adobe and Microsoft worked together to disable the desktop Flash functionality that is incompatible with touch, such as rollovers, within the Metro style experience. Much of Flash’s other functionality works well with touch.

Together we have also improved battery life with better support for PLM in the Metro style experience. Flash on Windows has already supported offloading potentially battery-draining video work to specialized video hardware for some time (link). This work improves responsiveness and performance as well.

Adobe and Microsoft have worked closely together for some time to address security and reliability issues (for example here, and here), sharing best practices like the SDL/SPLC and ASLR as well as information on hangs and crashes. By updating Flash through Windows Update, like IE, we make security more convenient for customers. Microsoft and Adobe remain committed to meeting the expectations of Windows customers with regard to the delivery of security updates. We are also working together on accessibility, manageability, and privacy.

The Flash Player included with Windows 8 is based on the full PC implementation and not a limited mobile subset, and there’s a clear path to make it available on the new chip architectures that Windows 8 supports. Adobe is committed to delivering this same Flash Player support for Metro style IE on both x86/64 and the initial delivery of Windows RT PCs (Windows running on ARM processors).

For the development community, platform continuity and technology choice are important. Flash in Metro style IE10 provides a bridge for existing sites to transition to HTML5 technologies where it makes sense and at a pace that is right for the experiences they want to deliver to their customers. HTML5 does not currently support, for example, some premium video content and game scenarios.

We will provide additional technical information in the coming weeks through the regular documentation channels, like MSDN and Adobe Developer Connection. These details will include how developers can test Flash content on their own sites in Metro style IE, and how to submit their sites for consideration for the CV list. This documentation will also include a best practices guide to help developers, designers, and content publishers create experiences with Flash that plays well on Metro style IE. These best practices will complement existing recommendations on authoring touch-friendly HTML5 sites.

“Do Not Track” on By Default in IE in Windows 8

In Windows 8, IE10 sends a “Do Not Track” signal to Web sites by default. Consumers can change this default setting if they choose. This decision reflects our commitment to providing Windows customers an experience that is “private by default” in an era when so much user data is collected online. IE10 is the first browser to send a “Do Not Track” (DNT) signal by default.

By changing the default Do Not Track setting in IE 10, we are broadening our commitment to providing consumers a great experience in Windows. And in the event companies don’t respect the Do Not Track signal, IE 10 will continue to include Tracking Protection list support to help consumers block unwanted tracking with two clicks. While some people will say that this change is too much and others that it is not enough, we think it is progress and that consumers will favor products designed with their privacy in mind over products that are designed primarily to gather their data.

You can read more about other actions underway with DNT here.

Vendor prefixes, and moving the Web forward from experimental to stable

With the Release Preview of Windows 8, IE10 adds support for non-vendor prefixed versions of standards that have reached Candidate Recommendation (CR) status since the Windows 8 Consumer Preview or should reach CR in 2012.

With this change, IE10 makes it easier for Web developers to write markup that works consistently across different browsers. Specifically, IE10 now supports the following W3C draft standards in their unprefixed form starting with the Release Preview: CSS transitions, transforms, animations, gradients, and CSS Fonts’ font-feature-settings property, as well as platform APIs such as the Indexed Database API (IndexedDB) and requestAnimationFrame().

We selected these standards after examining all the W3C draft standards IE10 supports and looking for standards that are stable (having no significant renaming or removal of properties/values expected), supported and interoperable across at least two browsers other than IE10 for the features’ core use cases, and already in use on the Web, including in their unprefixed form.

Browser vendors generally drop the vendor prefix once a specification reaches CR. For compatibility with sites and apps developed using the Windows 8 Consumer Preview and that rely on the Microsoft vendor prefix, IE10 continues to support the -ms- vendor-prefixed forms as well. Note that IE10 continues to support only the vendor-prefixed form of several other standards because these specifications are not yet sufficiently stable and interoperable, for example CSS Flexible Box Layout.

As a best practice, developers typically add an unprefixed version of a property to “future-proof” their pages. The following set of declarations is now ready for future browsers that support unprefixed CSS Transforms:

-webkit-transform: rotate(30deg);

-moz-transform: rotate(30deg);

-ms-transform: rotate(30deg);

-o-transform: rotate(30deg);

transform: rotate(30deg);

Other Key Platform Changes

In the Release Preview, we continue to improve performance. Web pages should just “stick to your finger” and remain fast and fluid while panning, zooming, and scaling content. The Chalkboard Benchmark shows the results of some of our performance work. It measures how efficiently a browser can perform these common touch actions by zooming in and out of a “chalkboard” while panning left, right, up, and then down. IE10’s performance here is a great example of Internet Explorer’s hardware acceleration in action.

Performance improvements contribute to great touch support, for example with full independent composition of Web page contents (fixed elements, subscrollers, animations, and video). We’ve also improved performance on low-end hardware; intensive sites now show much less flashing and flickering on low-end hardware. These improvements make IE10’s support for full screen video playback (in both HTML5 video and Adobe Flash Player) even better.

We’ve continued to improve the performance of the Chakra JavaScript engine. JavaScript intensive Web applications, like HTML5 games, will benefit from dynamic profile-based JIT, type-specialized code generation for floating point numbers, expansion of function inlining, and further tuning to reduce the idle memory footprint while reducing the observable pauses due to garbage collection.

We’ve also improved standards support in a number of ways. IE10 now has support for IVS/Emoji characters and the classList API and new reverse and alternate-reverse values of the animation-direction CSS property. DOM exceptions match the W3C WebIDL spec, and developers can use a constructor to create Blob objects, matching the W3C spec. We’ve also removed legacy DX filters from all modes.

HTML5 applications and sites can do more with touch via the MSGesture APIs that provide instantiable gesture event handling.

A Better Web Today, and Ahead

The opportunities continue for HTML5 to make both Web sites and applications better. Those opportunities are exciting for everyone on the Web.

To get to that Web sooner, we continue to recommend that developers update old and out of date patterns on their sites. Looking at the CV list you can find examples of sites that need shimming because they use out of date libraries (e.g. here) or rely on browser detection rather than feature detection. The compatibility problem reports we receive have more to do with sites detecting IE and sending it different content than they send other browsers than any particular issue in IE. Developers can find sample feature detection code patterns in several IE blog posts, including this one.

The quality and correctness of different browsers’ HTML5 engines continue to vary widely. We will submit updates to test cases to the W3C for all the features that IE10 now supports without a prefix. As members and co-editors of the CSS Working Group, we will work with our colleagues to move these specifications forward to Candidate Recommendation. We continue to contribute to the test suites under development at the HTML5 standards bodies to further the goal of interoperability and same markup. We’ve submitted and updated over 240 tests to them that you can view at the IE Test Center as well. As different browsers improve their support of the same markup to produce the same results, we can all realize the promise of HTML5.

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

—Dean Hachamovitch, Corporate Vice President, Internet Explorer

Comments

Anonymous
May 31, 2012
Win7 ?
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
Same, Win 7?
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
Please provide the ability to roam Favorites via skydrive so we can access our favorites anywhere we go..natively in IE10 and via BingBar for other versions and other browsers.
Anonymous
May 31, 2012
How about html5test result: http://html5test.com What is the current score or IE10 ver latest?
Anonymous
May 31, 2012
Win7 build please.
Anonymous
May 31, 2012
You guys for say that you dont implement incomplete standards. Than you say you will support -ms prefix to support incomplete standards? What a chaos! Now, if you are implementing some incomplete standards, then why dont you implement all the HTML5 standards undergoing approval process like other browsers? Like Maxthon and Chrome html5test.com/.../desktop.html
Anonymous
May 31, 2012
there is an os called Windows 7 which is also microsoft product supposed to have ie 10 like win8. Whatever win8 is coming who would give a sh#t
Anonymous
May 31, 2012
I would also like a Win7 build. Heck I'd also like IE to come back to Mac OS if you're feeling particularly confident ;)
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
Still no Win7 build. Still no word about GUI customization. Still no word about an useful framework for creating user extensions, neither for complete add-ons, or for user scripts or user css styles. And while I can't test it personally, I bet that IE10 also still comes up the worst on every single standards test or benchmark. As a long time IE user (IE9 is still my primary browser) and web developer: the IE team needs to set its priorities straight.
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
Great news! Hope it works the best on this platform and is fast for gaming.
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
@Slim Charles' comment is a great example of how to infer poor conclusions from good statistics. His affirmation is that indexing very, very large numbers of child elements within a single DOM element (in the case of this test, TEN THOUSAND CHILDREN) "are required by almost every next-generation interactive/rich web-application." .... really? There are lots of professional and hobbyist web developers reading this, and the vast, vast majority of us would be appalled at any kind of UI that would require us to have that many elements within a single parent. There is a definite performance failure here in IE10, so I took the JS, plugged it into JsFiddle and dialed down the test from 10,000 children to 1,000. Here are the results: Total elapsed time: 162ms Append: 1.00; 10ms Prepend: 1.10; 11ms Index: 11.60; 116ms Insert: 1.00; 10ms Remove: 1.50; 15ms Indexing 1,000 items takes 11.6x longer than append with a 1,000-child set. But, 10,000 items takes 136.3x longer with a 10,000-child set on my machine. So clearly the performance problem with indexing only manifests itself on very large child-node sets, which, as I said, is an extremely rare occurrence anyways. It's a fringe case. Warren.
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
I'm very disappointed that the RC of IE10 still lack a lot of features...I won't start to enumerate and you didn't even redesign the UI for the desktop version :( please add tracking protection list on windows phone 8
Anonymous
May 31, 2012
just out of curiosity, why isn't Silverlight installed by default ? some websites (e.g.: Photosynth.net) won't "just work"
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
You should also integrate Java, because some LOB apps won't work without that.
Anonymous
May 31, 2012
when Internet Explorer 10 for windows 7? Also in parallel, further development. Windows 8 from people not put kinda hate it.
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
Win 7 please. Honestly I would recommend Vista & XP while you were at it based on OS & browser market share.
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
WOW! You guys are amazing. I just recieve an email from Microsoft IE team that they have reactivated the connect bug report about the performance issue that Xero, Warren and Slim Charles(trolling copycat) are discussing about. I reported it a while back and it was closed. connect.microsoft.com/.../a-dom-manipulation-test-ie-performance (check the comments) Hopefully Microsoft resolve this issue in the final release. Congratulations for Microsoft and IE team, its a big day for Microsofties and big day for all of us !!
Anonymous
May 31, 2012
Hello IE Team, thanks for the release. > "IE10 now has support for (...) the classList API" How about dataset support? > "We’ve also removed legacy DX filters from all modes." Are you talking about the filter CSS property? I'm not sure how I'll see opacity and gradients if website sends IE=7|8 X-UA-Compatible header.
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
Slim Charles you forgot Opera 11.64 with result Total elapsed time: 136ms Breakdown (fraction shows time relative to append time): Append: 1.00; 38ms Prepend: 0.89; 34ms Index: 0.11; 4ms Insert: 1.29; 49ms Remove: 0.29; 11ms
Anonymous
May 31, 2012
FF12 results are juked too. He copy paste from connect ticket and changed FF 6 to FF12 Firefox 12results Total elapsed time: 569ms Breakdown (fraction shows time relative to append time): Append: 1.00; 60ms Prepend: 3.42; 205ms Index: 0.07; 4ms Insert: 3.18; 191ms Remove: 1.82; 109ms Which is also acceptable as its manipulating 10,000 children in single DOM parent 5 times in about half second! Compared to Safari its just 4 time slower. Shame on Microsoft though.
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
still so annoyed that we don't have ie10 for windows 7 yet, will we have to wait until it goes rtm? It will surely be buggy with so little public testing!
Anonymous
May 31, 2012
Comparison with other browsers on: ecmascript 262 conformance test ? sunspider ? dromeao ? ietestdrive speedreading ?
Anonymous
May 31, 2012
I share Sam's concern that IE10 on Windows 7 is not getting enough testing and the resulting release will be of poor quality. From Microsofts continued avoidance of discussing the Windows 7 release it seems like they intend to either release the final version with no public testing, or quietly drop it completely!
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
No Silverlight and Java!?! Win 7 please.
Anonymous
May 31, 2012
win7??????????????
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
If the user has enabled 'Show Tabs on a Separate Row' give him the ability to: 'Show Tabs on Top' ( of the location bar ). I'd really like the Tabs to be clickable when the mouse-pointer is on top edge, like Firefox... Would be difficult such an option?
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
I hope it has been fixed the BlurType (TM) that has been keeping me for updating to IE 9 and above. BlurType TM doesn't appear in Windows 8 Developer preview, but it appear on Customer Preview. I hope Microsoft has fixed in Preview Release [-o<
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
Like others have stated, this is really wrong. You stated that you will be releasing Internet Explorer 10 for Windows 7. I vaguely remember you stated you will release it before the final release. Meanwhile, you are working on a browser that has not gotten any community feedback on Windows 7, which, until Windows 8 really kicks in, will be its primary platform. This does not show commitment to compatibility and interoperability, this simply shows disrespect for your clients and and a not professional approach. Not every web developer is willing to compromise their entire operating system (or of their family, as well) in order to help you (and ourselves) test the newest iteration of your browser. Please, release the Windows 7 version of Internet Explorer 10 (preview, whatever) already and let us test it.
Anonymous
May 31, 2012
请在IE10中集成Silverlight！！！！
Anonymous
May 31, 2012
When can we expect a beta (preview) of IE10 in Windows 7? I'm going to be dual-booting Windows 7 and Windows 8 RP, but I also want IE10 goodness in Windows 7.
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
The comment has been removed
Anonymous
May 31, 2012
Still asking for Win7 support? LOL. IE10 is Win8 only, it should be obvious by now to everyone since MS refuses to release IE10 previews for Win7.
Anonymous
May 31, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
XPS.. Where is XPS Microsoft? Are you trying to discontinue it? Please provide XPS support in Browser 'View in browser' like PDF, Windows Phone (open XPS app from SkyDrive in Office Hub and save the file in Office Hub), iPhone (skydrive and memory) and Andriod.
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
Can you please make a loading indication when a user navigates an iframe? We are using iframes and there is not visual indication when an iframe is loading which leads to confusion and make users click several times until they see something happening. Now that we have websockets there is no reason not to show a loading indication for iframes.
Anonymous
June 01, 2012
Most of these things sound great and exciting. However there is one place, where you make me really sad. You are destroying DNT / Do Not Track by taking all of its meaning out of it. This is a huge step backwards for privacy. The whole point of DNT is to allow the user to explicitly and deliberately signal to sites that he does not want to be tracked. If a browser sends the signal by default, sites can no longer assume that DNT means that the user does not want to be tracked. The HTTP header then becomes additional waste bytes sent over the network. It would be great if all websites respected everybody's privacy more, but adding a new always-on HTTP header does not help that in any way what soever. The only thing you achieve is forcing less privacy on users using browsers that do support DNT properly. But I wonder if you already considered this and you just do this to destroy a privacy technology invented by a competitor.
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
@Slim Charles These particular set of tests are written by Ian Hixie, a Google employee, which exercise a small and specific set of DOM patterns. These tests are one measure of performance and may not necessarily correlate with real site performance impact. There is one specific test in the set which exercises a backwards traversal pattern, a pattern not nearly used as frequently as the forward traversal pattern by web developers, where IE is slower than others. While we expect this issue will have a limited impact on developers and real sites, we are investigating performance improvements to address this issue.
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
"Specifically, IE10 now supports the following W3C draft standards in their unprefixed form starting with the Release Preview: CSS transitions, transforms, animations, gradients, and CSS Fonts’ font-feature-settings property, as well as platform APIs such as the Indexed Database API (IndexedDB) and requestAnimationFrame()." Hang on a second, I think "gradients" should be omitted from here, as from my testing, and the developer docs, it seems like it still ships prefixed.
Anonymous
June 01, 2012
Uh, never mind the above post. Seems like I messed up the coding! Also, something not mentioned: now it supports the "to" syntax!
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
@WindowsVista567 (anonymous commentator) Maybe you should look at IE10's Acid3 results. http://acid3.acidtests.org/ Internet Explorer now scores 100/100.
Anonymous
June 01, 2012
I can never find an actual changelog for these previews, all I want is a list of the changes not paragraphs and paragraphs about a couple specific changes.
Anonymous
June 01, 2012
@WindowsVista567, IE9 since 9.0.2, also score 100/100 8-) Next milestone is to win the Google V8 test v8.googlecode.com/.../run.html
Anonymous
June 01, 2012
@Joe, I agree with you as this is just a rare benchmark. No real world scenario require 10,000 children attach, detach and index to a DOM in one go! Having said that, apparently Microsoft teams are on this issue and probably they would nail it down in the final release of IE10. Vote and keep following the issue status at connect.microsoft.com/.../a-dom-manipulation-test-ie-performance.
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
@EricLaw [MSFT] I didn't see the shockwave object when I clicked tools/manage add ons because I never selected show all add ons. but, if you remove the * from the allowed sites, you get annoyed with alerts to allow the add on to run. how do you get rid of those messages? I don't need to see them for every site. the best thing to do is just disable it completely.
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
My negative comment were deleted. So, here goes again. Where in IE10 are there the things in IE9 that I vitally rely upon, not just day by day, but minute by minute:

RSS feeds, to keep me up-to-date with changes to web sites that I need to constantly monitor as part of my job?
The Favorites Bar, which gives me one- or two-click access to the Web sites I use on a hourly basis (without me having to remember their spelling)?
My Favorites, a set of several thousand web sites that I have built up over years. It is my personal "Map" to the Web, organized into a folder hierarchy in such as way that I don't need to remember the names of thousand of web sites?

Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
The comment has been removed
Anonymous
June 01, 2012
Very fast on sunspider: IE10 RP: 123ms Chrome 19: 155 ms source: www.ghacks.net/.../internet-explorer-10-tech-improvements That is 26% faster than Chrome 19 on javascript
Anonymous
June 01, 2012
@Rob, Can you quote the results of the following:

Anonymous
June 02, 2012
Guys there's going to be a Windows 7 version lol. Each revision always backtracks at least 1 windows version. I beleive it will be available for Vista as well. No XP though.
Anonymous
June 02, 2012
The comment has been removed
Anonymous
June 02, 2012
@Reeses - There was already an official statement that said Internet Explorer 10 will not be coming to Windows Vista, so, your belief has no grounds. Also, we know there will be a Windows 7 edition of Internet Explorer 10, the official statement also stated that. We are just upset and worried about not getting a preview edition for us to test for regressions or to see that the bugs that were marked as resolved were indeed resolved.
Anonymous
June 02, 2012
The comment has been removed
Anonymous
June 02, 2012
Guys take a look here blogs.msdn.com/.../building-cross-browser-plugin-free-experiences.aspx Microsoft shift every month. Please make a soild policy .
Anonymous
June 02, 2012
Please add reopen closed Tab in MetroIE, that feature is really missing!
Anonymous
June 02, 2012
The comment has been removed
Anonymous
June 02, 2012
The comment has been removed
Anonymous
June 02, 2012
@Nick Silverlight is mostly used for internal corporate applications. It isn't on many public-facing websites, but that doesn't mean that it wasn't widely used for intranet applications where the user's environment was strictly controlled by the IT department. In those cases the general public adoption rate for Silverlight was never a concern, and it allowed for rapid development because developers could use their existing C# skills instead of learning standards compliant HTML5 (which is generally a lot more complicated to write and harder to debug and maintain).
Anonymous
June 02, 2012
Why does IE10's development take so long? Seriously, Chrome, Firefox can release new version every week. People want want to try new things, and rapid development lifecycle. No wonder Microsoft is loosing market share.
Anonymous
June 02, 2012
@chefgon I'll agree with you that silverlight was used in intranet apps on corporate networks where hardware specs could be dictated. However we've now had 3 years of tablets by Apple, RIM and Google that have saturated the market. None of them support silverlight right now nor will they. Microsoft has ZERO percent of the tablet market and now silverlight developers are upset that it won't be supported on tablets. The writing has been on the wall for years now... There will not be silverlight on tablets... Get over it!
Anonymous
June 02, 2012
The comment has been removed
Anonymous
June 02, 2012
The comment has been removed
Anonymous
June 02, 2012
@Kevin At least it should continue playing when on wifi and a desktop/laptop type device. On a tablet type device with a telecom provider it would not seem strange to stop downloading and playing when the screen turns of or even when you start to do something different in the browser or an app.
Anonymous
June 02, 2012
Is it me, or there's a bug on CSS:hover? Everytime I hover elements they stay hovered and don't change back.
Anonymous
June 02, 2012
@Rob - I disagree completely. If the user closes the tab or browser then yes the audio should stop but until the the user does so it should Definately continue! It's a bug for sure. If Microsoft had open public bug tracking we could submit a simple test case and we could all verify the bug and track it's progress. However we all know that Microsoft fears open bug tracking and won't allow this. It's a condition called dinasour-itus. Better yet if IE10 was available to test on Windows 7 - you know the OS that we all use will and can actually test on?! Please separate IE from windows 8 - we don't want windows 8 and we certainly don't have time or interest in alpha testing an OS for you on our primary workstation. #TiredOfWindows8AndItHasntEvenLaunchedYet
Anonymous
June 03, 2012
The comment has been removed
Anonymous
June 03, 2012
The comment has been removed
Anonymous
June 03, 2012
wonder what unedited version of comments here would look like ???????????????????????
Anonymous
June 03, 2012
The comment has been removed
Anonymous
June 03, 2012
The comment has been removed
Anonymous
June 03, 2012
The comment has been removed
Anonymous
June 03, 2012
The comment has been removed
Anonymous
June 03, 2012
Why can't we have an OPTION in IE10 to use full subpixel anti-aliasing instead of the grayscale-only anti-aliasing it uses? Please modify the DirectWrite renderer to use it. For PCs, there is no reason why grayscale anti-aliasing should be used. Please reply.
Anonymous
June 03, 2012
The comment has been removed
Anonymous
June 03, 2012
The comment has been removed
Anonymous
June 03, 2012
It's really impressive how Microsoft alienates its own developer base. I guess we should all be developing WinRT by now? Guess what? We switched to HTML / JS. No plans to support WinRT.
Anonymous
June 04, 2012
The comment has been removed
Anonymous
June 04, 2012
@Xero, V8: 2589,details below:- Richards: 3061 DeltaBlue: 2069 Crypto: 4681 RayTrace: 2700 EarleyBoyer: 4323 RegExp: 1080 Splay: 1151 NavierStokes: 4690 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxx Peacekeeper: 1049 (html5 tests 4/7)
Anonymous
June 04, 2012
Goren: those are relative performance numbers, they mean nothing on their own without comparison numbers for other browsers. (you could be running ie10 on a core i7 2600k 5ghz, and get better numbers than someone running chrome on his netbook). HTML5test score only jumped up 5 or so to 319, which is worrying. IE is again the tail end in standards support, or at least, that's how the public will perceive it.
Anonymous
June 04, 2012
The comment has been removed
Anonymous
June 04, 2012
The comment has been removed
Anonymous
June 04, 2012
The comment has been removed
Anonymous
June 04, 2012
The comment has been removed
Anonymous
June 04, 2012
I do no believe in unfixable form submission and session handling. Anyway not even worth it for the lols. Time to move on.
Anonymous
June 04, 2012
You didn't make any sense, you know that right?
Anonymous
June 04, 2012
The comment has been removed
Anonymous
June 04, 2012
@Arieta "The Test262 is a standards support test like html5test." You must be kidding. Test 262 is a standards conformance test by a real standard organization which test many thousands of elements of de entire ecmascript standard and its features to determine conformance. HTMLtest is a private test that has a limited arbitrary selection of tests and gives a very arbitrary value to those tests. It does not test conformance but rather tests which browserbuilder is trying to influence W3C the most that their interpretation of still unfinished standards should prevail.
Anonymous
June 04, 2012
SUPPORT SILVERLIGHT!!!!!!! IT´S YOUR OWN TECHNOLOGY
Anonymous
June 05, 2012
No Silvelright??? That's not disappointing, that's frustrating!
Anonymous
June 05, 2012
The comment has been removed
Anonymous
June 06, 2012
@Ronald, blog is not the bug tracking tool. Microsoft connect is meant for that purpose. Secondly, this blog system is developed by third-party; Telligent. Telligent have several blogging solutions. The one running on WindowsTeamBlog.com enforce the users to sign-in and the session never expires. The second kind of product is this one on MSDN blogs, they allow users to post comments without login as well. To prevent from being misused, they have implemented this restriction that the session would be expired after 15 minutes or so. But if you login, the comment session will not expire.
Anonymous
June 06, 2012
同样的链接预览代码 <meta name="description" content="我才是真正的描述" /> <link rel="image_src" href="beta.png" /> 在windows 8 CP版本中本地调试可以实现效果在windows 8 rp版中本地调试效果出不来部署到网站之后能够出来效果，为什么在windows 8 RP版本地链接预览效果出不来？求解释
Anonymous
June 08, 2012
The comment has been removed
Anonymous
June 09, 2012
The comment has been removed
Anonymous
June 13, 2012
The comment has been removed
Anonymous
October 30, 2013
necesito el programa actualizado para hacer mis tareas
Anonymous
October 31, 2013
ou est le menu outils je c c'est bête mais j'ai besoin d'aide !!!

Partager via