Updates to the Internet Explorer Testing Center
With the release of Internet Explorer 11 Preview as part of the Windows 8.1 Preview, we have updated the IE Testing Center to include new test cases for the standards supported in IE11, advancing browser interoperability. As Web developers are building for more browsers and devices, they want to be more efficient by using the same markup across their sites. Having clear tests of standards support in browsers helps drive clarity and completeness for both the Web community and browser vendors, leading to a more interoperable Web.
1199 new test cases submitted to standards organizations
We have added 1199 test cases on the IE Testing Center for Web Crypto, PreFetch, High Resolution Timers, Navigation Timing 2, Performance timeline, Canvas, JavaScript, Media Source Extensions, Pointer Events, Page Show and Page Hide, DOM4 Mutation observers, Document.all, WebIDL binding, and Flex box. Our 570 JavaScript test cases support Ecma International’s ECMAScript Sixth Edition draft specification (also known as ES6) as well as ECMA-402 JavaScript Internationalization.
We’re submitting these new test cases to standards bodies through their official process for review, feedback, and inclusion into the official test suites.
In addition to our internal test case development, we also participate in public W3C sponsored events through Test The Web Forward. At these events we work with the developer community and other browser vendors to write tests that move W3C proposals forward. The event last April was sponsored by Microsoft and took place in our Seattle offices. Together we were able to contribute 514 new tests in just one day.
Feedback on the test cases
As always, we look forward to working closely with standards bodies and their membership to make the Web better through the Web standards process.
Each Standards Organization has methods for providing feedback. For W3C test cases, please use the W3C mailing list for the appropriate working group. For JavaScript test cases, please submit your feedback in the ECMAScript bug database.
We encourage other browser vendors to help the W3C finish the HTML5 specification by providing additional tests to the official HTML5 testing task force.
Thank you,
Matt Gradwohl & Rajkumar Mohanram
Internet Explorer Test Managers
Dinesh Chandnani
JavaScript Test Manager
Comments
Anonymous
July 01, 2013
Any news on MathML?Anonymous
July 01, 2013
Hey, Web crypto (msdn.microsoft.com/.../dn302338(v=vs.85).aspx) and ECMA i18n (AKA real date formatting)! Hurrah!Anonymous
July 01, 2013
> Document.all Huh?!Anonymous
July 01, 2013
You gotta be kidding, what standard includes document.all? It's that long ago Firefox got liberated from that hackery.Anonymous
July 01, 2013
The comment has been removedAnonymous
July 02, 2013
www.w3.org/.../infrastructure.htmlAnonymous
July 02, 2013
" We're submitting these new test cases to standards bodies through their official process for review, feedback, and inclusion into the official test suites. " Microsoft CSS2.1 tests got review, feedback and, often, proposed corrections for tests which could be rehabilitated. More than 12 months ago. Often, more than 18 months ago. In some cases, more than 24 months ago. You got reviews, feedback on those Microsoft CSS2.1 tests in emails. In the public-css-testsuite mailing list. In the open issues wiki page. Then, in Shepherd system. And then in the known bugs wiki page. You still have not acted accordingly for a majority of those CSS2.1 tests. Creating and submitting new tests is one thing; having them reviewed by appropriate mailing list of CSSWG (public test suite mailing list), and then dealing with these or adjusting these in a timely manner thanks to feedback is another. Currently 232 tests submitted by Microsoft to the CSS 2.1 test suite are in need of coding adjustments (minor or more serious): test.csswg.org/shepherd/search/testcase/spec/css21/author/microsoft/status/issue/ Currently 52 tests submitted by Microsoft to the CSS 2.1 test suite are incorrect, wrong: test.csswg.org/.../Incorrect Currently 67 tests submitted by Microsoft to the CSS 2.1 test suite are imprecise: test.csswg.org/.../Precision Currently 31 tests submitted by Microsoft to the CSS 2.1 test suite have been rejected: test.csswg.org/.../rejected Incorrect tests, imprecise tests and rejected tests have often unfairly advantaged IE over other browsers. And it has been like that since CSS 2.1 test suite conformance results 1.0, dated march 23rd 2011. Gérard TalbotAnonymous
July 02, 2013
If you people would actually look stuff up before complaining you'd know that the change to document.all is a good oneAnonymous
July 02, 2013
That is probably why Microsoft refers to the W3C tests and not their own. The number of tests submitted by gtalbot is ZERO.Anonymous
July 02, 2013
@@ Gérard Talbot I don't know how many tests Gérard submitted, but he's still been contributing to the web community for years in various ways (pointing out problems like he did here, bug reporting, etc). That easily beats the contributions of random nameless trolls in my books.Anonymous
July 03, 2013
Does this mean ECMAScript 6 support in Internet Explorer 11 ? OK, that alone made me smile :) I've posted a comment on your previous IE 11-related post, asking about support for some web features for web designers and developers, I hope it gets approved soon...Anonymous
July 03, 2013
> The number of tests submitted by gtalbot is ZERO. Even if what you were saying, you anonymous person, was true, it would still not weaken my criticism about Microsoft submitted CSS2.1 tests: a majority of submitted CSS2.1 tests by Microsoft for review have been reviewed (in emails, in mailing list, in 2 wiki pages, in Shepherd system) and have been waiting for appropriate follow-up action for 12-24 months from Microsoft. I authored 447 tests with 195 of them reviewed and approved so far; 248 of them are waiting to be reviewed. I authored 1121 reference files. I am "co-owner" of 112 support files. Anyone can verify these numbers all by himself by querying Shepherd system: test.csswg.org/shepherd/search/author/gtalbot/ Tests submitted and/or owned, since May 17th 2011: test.csswg.org/source/contributors/gtalbot/submitted/
A minority of tests in that IE test center have issues:
- markup validation errors, often due to a mistake in their doctype declaration
- non-streamlined tests
- at first glance, some are doubtful tests (and this is more serious): one example is the sole prefetch test recently added to IE test center: this one is mind-boggling to say the least
- inconsistency when choosing spec: prefetch/prerender is not even a Draft or Working Draft in Web Performance specs yet and Microsoft creates a test. (<link rel="prefetch" is an HTML5 attribute though: www.whatwg.org/specs/web-apps/current-work/#link-type-prefetch ) On the other hand, border-image has been in a Candidate Release spec for over a year now and no test - zero - added to IE test center or submitted to standards bodies. Gérard Talbot
- Anonymous
July 03, 2013
Will Internet Explorer 11 support these: - Opus audio codec http://caniuse.com/#feat=opus
- @supports at Rule -- CSS 3 Conditional Rules
- CSS Intrinsic and Extrinsic Sizing -- CSS 3
- HTML datalist element without buggy behavior: caniuse.com
- new HTML5 form input types:
- number -- with increment/decrement buttons (missing in IE 10): caniuse.com
- color
- date, time, datetime-local
HTML details element caniuse.com
HTML meter element caniuse.com
<a download> attribute davidwalsh.name/download-attribute ? Most are already supported in either the latest Chrome or Firefox or will be soon. And I hope that the CSS Variables and CSS Mixins specs (or whatever they're called now) can be approved soon, so there won't be any need for CSS preprocessors like SASS / LESS / Stylus someday, and CSS libraries (like Compass, and nib) can be created in one format.
Anonymous
July 04, 2013
i want update internet explorerAnonymous
July 04, 2013
Please load chrome or another webkit browser.... type document.all in the consoleAnonymous
July 05, 2013
@Rob: Chrome has more bugs than IE10 when it comes to standards.Anonymous
July 05, 2013
@Arieta - According to the W3C becnhmarks, Chrome has even more bugs than IE9Anonymous
July 05, 2013
Rob ^_^, When I load a webkit browser or any DOM 1 Core compliant browser and type in a javascript console: document.getElementsByTagName("") " getElementsByTagName Returns a NodeList of all the Elements with a given tag name in the order in which they are encountered in a preorder traversal of the Document tree. Parameters tagname of type DOMString The name of the tag to match on. The special value "" matches all tags. " www.w3.org/.../level-one-core.html then I get a list of all nodes in the document. I fail to see why document.all has to be supported or how or what document.all does more or better than the already working and available document.getElementsByTagName("*"). I fail to see any relevance, signficance or importance in supporting document.all . If other non-IE browsers start to implement document.all, then you can expect a lot of faulty code forks, incorrect browser sniffing, pages redirections, etc to happen in a lot of websites. Gérard TalbotAnonymous
July 05, 2013
Except Firefox, almost all the browsers support document.all: IE, Safari, Chrome, Opera..Anonymous
July 05, 2013
Firefox supports document.all in quirks mode (no doctype, or outdated one). data:text/html,Hello<script>alert(document.all.length)</script> shows "4". document.all is in the (emerging) HTML5 standard, only for web compatibility purposes. The standards defines it in a special way, also for compatibility reasons - typeof document.all === "undefined" evaluates to true (and similar and their opposites). This was done to eliminate browser sniffing using document.all detection for triggering Internet Explorer specific code. Some websites do not check for existence and simply use document.all, so in order not to break them, browsers should silently support document.all, even in standards mode (all of them do, except Firefox).Anonymous
July 05, 2013
Hey, what about Apple Safari? Even though Safari 6.1 or 6.2 (something like that, forgot...) does not support on Windows 8/8.1, we can still test Safari on Macs and not just that, but testing all browsers on Macs and PC's comparing to Internet Explorer 10/11. So that way, we can still get a sense of how efficient/smooth each browser is regardless of the operating system. This is all I just want to point out. Apple Safari 6.1/6.2/(something the latest...) vs. Internet Explorer 10/11. Thanks...Anonymous
July 06, 2013
The comment has been removedAnonymous
July 06, 2013
I think that IE testing team should address the problems with tests that Gérard Talbot highlighted.Anonymous
July 06, 2013
I don't see the issues fduch does and many of them sound graphics driver related. But I'd love to see the MRU for images persist beyond the current page/tab groupAnonymous
July 07, 2013
The comment has been removedAnonymous
July 08, 2013
I just updated,Anonymous
July 08, 2013
The comment has been removedAnonymous
July 09, 2013
Speaking of which, can someone test if IE11 fixes the handle leak / memory leak problem?Anonymous
July 09, 2013
The problem you have but many already have confirmed on this blog not to have seen at all even with a ton of tabs open. You might look to your config rather than expect a solutionAnonymous
July 10, 2013
Don't live server sent events out. All your competitors already implemented it and is very important from the developer stand point. Webgl is more for game creators but we, the developers we want server sent events to be available in all browsers. I am not so enthusiastic about Webgl but server sent events is a must.