Status roadmap update: srcset, <main> element, and date inputs in development

Today we’re updating our platform roadmap with a few more features that we’ve started working on:

Responsive Images: image srcset

To take advantage of high resolution screens, it’s desirable to provide higher resolution image resources. While today’s devices come with all sorts of different resolution screens, it’s important to be able to provide the right resource for the device’s capabilities for optimal experience and performance. We have therefore begun work on implementing the srcset attribute for image elements, enabling alternate image resources based on the device’s DPI scaling factor:

We’re starting with srcset pixel density descriptors for the broadest interoperability, but we’re looking at other features like width/height descriptors and the <picture> element for possible implementation in the future.

Date input controls

Inputting dates in a form is common practice on the Web. We’re beginning the implementation of a variety of new input controls for basic date picking. These controls will use the standard HTML5 types and provide UI that’s friendly to your input device, like our other HTML5 input controls.

This work is “phase 1” of 2. This first phase includes date, week, and month controls. The second phase (not yet in development) includes time related inputs. We’ll update you when work on phase 2 begins.

<main> element

We introduced a number of HTML5 semantic elements in IE9. We’re now adding support for the <main> element, which represents the main content of the document or application.

As always, check status.modern.IE for the latest on our development roadmap, vote for features on User Voice, and give us feedback on how we’re doing at @IEDevChat.

Jacob Rossi
Senior Program Manager

Comments (15)

  1. Yannick says:

    Date input types. Yay! Anyway, I guess these are coming with IE12? How is it going with the new developer tools? Will they ship tomorrow?

    Also, reports that, while loading, there are 182 features found, however, there is 1 feature that's not part of any of the 5 categories (Not planned, under consideration, development, etc). Because it only shows 181 features when all of these are selected.

  2. FremyCompany says:

    Cool. My only fear is the new input types will respond to basic styling (borders, background images, fonts, …) in a way that's incompatible with normal inputs (like type=file did back in time). Do you have any idea of how this will render already? I hope it looks like a text field by default ^_^

  3. __hAl__ says:

    The article could do with some early renderings of these features.

    That would give us better opportunity to comment on the feature.

  4. seimis says:

    Two of those suggestions were mine! Thanks.

    However, input type=date and type=time are the only ones in the HTML5 spec. HTML5.1 adds datetime, week and month, but datetime-local is removed from the spec, yet listed on

    Should be fixed, as I hope you're not planning to support removed spec.


  5. Justin Avery says:

    Really happy to see the picture element is kicking off now with the x descriptor and moving on from there.

  6. aziz.sallam says:

    adding inline picture  to make client side  entry validation  auto for unicode  date and currency ,etc  in html5  may be a great  

  7. aziz.sallam says:

    adding a   validation  listener  for  client side standard input fields (date,numeric fields,text,)  that comply with  programmer format  picture  is  wise   & also with data annotation or  api  in server side  

  8. seimis says:

    Now I only miss <time>, <input type="color">, <output>, <meter>, <details>/<summary>, <menu> and <dialog> from the HTML5 spec, along with some attributes like a[download], minlength, dropzone, table[sortable], style[scoped] and ol[reversed].

  9. Jacob Rossi [MSFT] says:

    @Yannick – These will likely show up first in a preview build of IE for Windows 10 and on RemoteIE.  On dev tools, check back here…soon. 😉 Thanks for the bug report on – someone submitted a pull request to us to fix this, which has been mreged.…/167

    @FremyCompany – you'll be able to style these in-place and they'll appear similar to a text box as you suggest. Right now, we're not planning on exposing styling or the control popups themselves. These controls will match the look and feel of the controls used elsewhere on the system.

    @__hAl__ – we're sharing this so early that we don't yet have any renderings yet. But watch @IEDevChat on Twitter and we may share some progress as we go along. 🙂

    @seimis – we're still building our plan for the time related controls.  Spec status will certainly influence that. However, interoperability will also.  Currently, there are browsers that implement datetime-local but not datetime. For your other features, definitely go post/vote on

  10. Yannick says:

    @Jacob Rossi [MSFT] – "On dev tools, check back here…soon. ;-)"

    I'll take that as "yes, check back in a couple of hours as we publish a changelog" then. 🙂

  11. Brian LePore says:

    How will IE handle error handling in regards to srcset? In early (current?) WebKit/Blink if the browser only supported the pixel density descriptor and not the weight, and weight was first (and potentially if there was no valid pixel density descriptor , I cannot recall) then the browser would load the very first image listed in srcset, rather than just ignore everything and use the original src image.  I found myself needing to include the src image with the width descriptor as they very first possible image (and maybe including a 1x pixel density descriptor) to work around this bug.

    Serves me right for being bleeding edge, but still, would be nice to know how things will behave.

  12. Remo says:

    and when is coming preserve-3d….?

  13. Asbjørn says:

    Srcset? Really? Why did you have to choose the lousy, Apple-proprietary "solution". The picture element is a much more elegant solution that doesn't require a giant text string in a specific format. Srcset is an abuse of attributes that should not be allowed.

  14. NumbStill says:

    @Asbjørn –

    Safari, Chrome (34) and Firefox have implemented or are implementing srcset. Chrome (38) has also implemented the picture element. Firefox is implementing it, too. I believe others are as well. These two ways complement each other.

  15. André Neves says:

    Great solution, also avaliable in some versions of chrome, safari and FF.

Skip to main content