Updates to our platform roadmap
Continuing our commitment to openly sharing our platform roadmap via status.modern.IE, today we’re announcing another round of updates to our plan. These updates include new ECMAScript, Networking, Performance, Media, CSS, and DOM features under consideration and in development:
| Feature | Status |
| Math Built-ins (ES6) | In Development |
| Number Built-ins (ES6) | In Development |
| String Built-ins (ES6) | In Development |
| Object Built-ins (ES6) | In Development |
| RegExp Built-ins (ES6) | In Development |
| Classes (ES6) | In Development |
| Template Strings (ES6) | In Development |
| dppx Unit for resolution Media Query | In Development |
| DOM Event Constructors | In Development |
| WAV Audio Support | In Development |
| Meta Referrer | In Development |
| WeakSet (ES6) | Under Consideration |
| Spread (ES6) | Under Consideration |
| Tail Calls (ES6) | Under Consideration |
| Subclassing (ES6) | Under Consideration |
| Modules (ES6) | Under Consideration |
| SIMD (ES7) | Under Consideration |
| ASM.js | Under Consideration |
| Clipboard API | Under Consideration |
Follow status.modern.IE for continual updates as our plans evolve for the Web platform in IE. Additionally, IE feature statuses are also integrated into caniuse.com via our open data feed. You can also help us make this a valuable resource for developers by contributing to the open source project. As always, ask us questions and give us feedback via @IEDevChat.
Jacob Rossi
Senior Program Manager
Update 9/18/14 - Added Clipboard API as Under Consideration
Comments
Anonymous
September 18, 2014
That's great. Could you provide some guidance at how frequently we should expect to see the dev-channel being updated and which features would be able to be delivered as an incremental update (like the recent batch of webgl features), and which would need a major upgrade of the browser (i.e. a new user agent string)? This information helps web developers that are considering adopting new platform features.Anonymous
September 18, 2014
Math Built-ins! Does it mean Microsoft will consider native MathML support as well? That would be revolutionary!Anonymous
September 18, 2014
@Peter: MathML is still "Not currently planned" on status.modern.ie, and that's too bad. Hey, IE team! Taking your time for MathML is all right, and we all understand that you have more pressing features to implement, but don't you think you are taking just a little TOO MUCH time? After all, MathML support IS part of HTML5, and for good reasons. When will we be able to blog a few equations without pulling in big chunks of javascript? Just put someone on implementing the parsing and required glue code, let Office's math renderer do the heavy work, and ask the community to give you lots of test cases. (There are people working on MathML renderers, e.g. the Mozilla one, and I'm sure they would be interested in giving you a hand). Are you already so shorthanded that you can't find a greenhorn to work on this? Or is your code so messy that adding a few tag to the parsers would likely break the rest? Come on, I'm sure that"s not true.Anonymous
September 18, 2014
@Peter: The Math object built-ins added in ES6 bear no relation to MathML. MathML is still listed as Not Currently Planned on Status IE: status.modern.ieAnonymous
September 18, 2014
When will we get support for h.265 codecs for use in pictures (h.265 Main Still Picture profile) and html video (h.265 Main profile) ?Anonymous
September 18, 2014
asm.js pleaseAnonymous
September 19, 2014
I'm so used to mediocrity from MS that seeing asm.js on the list caught me off guard. The new MS is better than the old, definitely. But now, how about implementing MathML?Anonymous
September 19, 2014
Several years ago, I would only comment on IEBlog to chastise the team for their ineptitude. Today, I thank you for making sure recent releases of IE are reasonably up-to-date. ES6 is one of the most important new Web technologies, and knowing that I'm able to start architecting around it is an incredible feeling! I really hope the "Under Consideration" items make it in for IE12. At least the ES6 and SIMD stuff. Thanks again!Anonymous
September 19, 2014
SIMD is ES7 dude! Hold your horses.. You are acting like a kid who wants just everything! Be a man duuuuude!Anonymous
September 19, 2014
The comment has been removedAnonymous
September 19, 2014
I'm glad to see on the status page that getUserMedia(); is in development. With some luck it will land on windows phone/ie before iOS delivers it! :-) Keep up the food work and get the windows ream to pish out the windows 9 start button! So many users won't buy windows 8 because of this massive fail.Anonymous
September 19, 2014
the link in "feedback via @IEDevChat." misspells twitter and goes to a spammy page other than that, nice to see this roadmapAnonymous
September 20, 2014
Good that you are adding more platform features. But - you seem to have missed the point a having a developer channel. The IE Dev channel build has not seen a single update since its initial release. That was not my expectation, that is for sure. Looking forward to IE12, though - especially if the rumors are to be believed and it has a new UI and better extensibility.Anonymous
September 20, 2014
Great to see more added to the status website. However, what would be even better is you guys acutaly sharing your roadmap. Sure, it's nice to see what features are being worked on, but that's not realy a roadmap. A roadmap has dates, and we don't get to see any of that. It would be great if you guys just told us when we can expect this, even just in beta channel. The IEDC has been released 3 months ago now, and we haven't seen 1 single update. I realy hoped you guys would use it to push the things your working on to the public. Make it better. However, IEDC has become, due to updates to IE11, dated. Most of the things in IEDC are now already in IE11 (or partialy, like WebDriver). Only GamePad API is left behind in IEDC. It would be great if we got at least, after all this time just 1 respons with a date. I know you guys aren't to keen on commenting here (for whatever reason that is). But please, do it, even if it is just once.Anonymous
September 20, 2014
MathML fans, you have some impressive JavaScript tools for showing math on the Web including the recently released KaTeX: http://khan.github.io/KaTeX/ One advantage of those is that they behave similarly on downlevel browsers (down to IE8).Anonymous
September 21, 2014
So you're adding support for WAV audio format but not Ogg Vorbis, WebM Vorbis, Ogg Opus or WebM Opus? en.wikipedia.org/.../HTML5_Audio The decision to blatantly and intentionally force closed non-free codecs on the world will not only fail though when the government actually becomes for the people by the people the trial won't take months since Microsoft's for-profit policies are so blatant. I believe collusion with Apple, RAM manufacturers and others in the industry won't help any on that day. It's time to change your ways and fast.Anonymous
September 21, 2014
Hi, When do you think a LLVM backend for C# will be implemented? There is no point supporting Asm.js without this. Thanks! visualstudio.uservoice.com/.../3725445-xna-5Anonymous
September 21, 2014
Hello! What you have added roadmap upgrading IE12 new features, it is certainly very good, but why do not you lay out a new alpha or beta version of the browser? When will be presented to the assembly IE12, which will include the previously stated options? And most importantly, I did not understand on what OS will run IE12?Anonymous
September 21, 2014
Hello! What you have added roadmap upgrading IE12 new features, it is certainly very good, but why do not you lay out a new alpha or beta version of the browser? When will be presented to the assembly IE12, which will include the previously stated options? And most importantly, I did not understand on what OS will run IE12?Anonymous
September 22, 2014
Dear friends! If you approve of my idea and want to see the correct display of WebP format in IE 12, please support my feedback! connect.microsoft.com/.../979075Anonymous
September 22, 2014
Will you be discussing or getting feedback on any of the upcoming UI changes in IE12, on this blog? I'm still desperate for a gesture or function to quickly get to the top or the bottom of very long pages in touch-based IE ("Immersive" IE on Win8, and IE on Windows Phone). There's no Home or End button to press in those situations, or any way to 'grab' a scroll bar to quickly move to the top or bottom. It's a huge usability issue given so many "endlessly scrolling" pages that can get very long, but which have controls at the top.Anonymous
September 22, 2014
Page Visibility v2 support? This is badly needed for mobile web especially. dvcs.w3.org/.../Overview.htmlAnonymous
September 23, 2014
@Jeffrey Gilbert, If something is missing from status page, feel free to log it in their issue tracker: github.com/.../issues BTW, Page Visibility v2 is still an Editor's draft.Anonymous
September 23, 2014
The comment has been removedAnonymous
September 24, 2014
@Edward - Whenever did they say that they implemented WebGL 1.0 completely? There isn't a single browser that supports WebGL 1.0 completely. Neither should IE. Anyway, Chrome manages to get 2 timeouts. So please, don't lie (and I'm talking about the 1.0 100% statement).Anonymous
September 25, 2014
@Yannick, I am sorry that I hurt your feelings. But wouldn't it be nice if IE fix those bug? When you said "Neither should IE", it's kind of feel wrong, isn't it? Also, for IE there are total 5487 tests and for firefox, it shows total of 5506. Is it the browser sniffing or something on Khronos end or some features the IE is missing?Anonymous
September 25, 2014
A bug in IE: new Date(2100, 0, 1, 0, 0, 0, 0).valueOf() should return 4102473600000, IE11 with all updates return 4102437600000. Following twelve DateTime tests cases are failed by IE, while non-IE browsers pass it: if (-2208960000001 !== new Date(1899, 11, 31, 23, 59, 59, 999).valueOf()) { $FAIL("#1: Incorrect value of Date"); } if (-2208960000000 !== new Date(1899, 12, 1, 0, 0, 0, 0).valueOf()) { $FAIL("#2: Incorrect value of Date"); } if (-2208960000000 !== new Date(1900, 0, 1, 0, 0, 0, 0).valueOf()) { $FAIL("#3: Incorrect value of Date"); } if (28799999 !== new Date(1969, 11, 31, 23, 59, 59, 999).valueOf()) { $FAIL("#4: Incorrect value of Date"); } if (28800000 !== new Date(1969, 12, 1, 0, 0, 0, 0).valueOf()) { $FAIL("#5: Incorrect value of Date"); } if (28800000 !== new Date(1970, 0, 1, 0, 0, 0, 0).valueOf()) { $FAIL("#6: Incorrect value of Date"); } if (946713599999 !== new Date(1999, 11, 31, 23, 59, 59, 999).valueOf()) { $FAIL("#7: Incorrect value of Date"); } if (946713600000 !== new Date(1999, 12, 1, 0, 0, 0, 0).valueOf()) { $FAIL("#8: Incorrect value of Date"); } if (946713600000 !== new Date(2000, 0, 1, 0, 0, 0, 0).valueOf()) { $FAIL("#9: Incorrect value of Date"); } if (4102473599999 !== new Date(2099, 11, 31, 23, 59, 59, 999).valueOf()) { $FAIL("#10: Incorrect value of Date"); } if (4102473600000 !== new Date(2099, 12, 1, 0, 0, 0, 0).valueOf()) { $FAIL("#11: Incorrect value of Date"); } if (4102473600000 !== new Date(2100, 0, 1, 0, 0, 0, 0).valueOf()) { $FAIL("#12: Incorrect value of Date"); }Anonymous
September 26, 2014
@Edward - Because I say something, doesn't makes me a fanboy. IE shouldn't support WebGL for the full 100%, neither should any browser. Idem dito for prety much every modern "standard" like CSS3 and HTML5. Why? Because they aren't finished. WebGL 1.0 is done, through it can use a lot of improvement. Missing support isn't a bug either, by the way, so no, they don't have to fix it, because there is nothing to fix, just more stuff to support someday in the future. But then again, you didn't answer my question: where and whenever did the IE team promis to support WebGL 1.0 for the full 100%?Anonymous
September 26, 2014
@Yannick I didn't called you a fanboy. It's your own guilt showing you things in between the lines. Also, you don't know what are you talking about. The last comment about "not conforming with standard being some kind of a good thing" makes you look like a joke. Now take a chill pill and go back to your PS4 sunnyboi! oh sorry I mean your Xbone (ahem).Anonymous
September 27, 2014
@Edward - "I am sorry that I hurt your feelings" is calling someone a fanboy. And now you're doing just the same thing you say Im doing: add things in between the lines... I never said that IE shouldn't support standards and that that would be a good thing. I said that there is no point in supporting HTML5, CSS3 or WebGL completely because THEY AREN'T STANDARDS or simply need a lot of work. As long as something isn't a standard, it's subject to change, double work. Or else we get the mess Webkit has made with prefixes for everything.Anonymous
September 29, 2014
The comment has been removedAnonymous
October 01, 2014
For those who love MathML, you can vote for this feature on wpdev.uservoice.com/.../6508572-mathml