This is helpful for other reasons too. Currently type="number" is great and shows the correct keyboard on mobile devices. However any attempt to set a partial value, or use any of the selection properties/methods fails. Having the inputmode attribute available would mean we can choose the best input device keyboard but not suffer the side-effects of setting the field as number.

While I'll agree that supporting this as a CSS property across the board would be awesome, the primary concern is for textareas. If this was only added by default for textareas and not even controllable via CSS it would still be a massive improvement over the current textarea rendering... and still be considered a massive success! IMHO. (PS my original textarea only idea request was merged into this one)

They say that "Necessity is the Mother of Invention"... as a result I've provided a jQuery plugin implementation to provide this feature to current Internet Explorer users. It would just be awesome though if Project Spartan supported this natively!

I disagree. There is a very distinct difference between whether a variable (think member of an object/map) is null or undefined.

This is particularly important when reading a JSON object where the "lack" of a property even being passed (e.g. saving bytes on the network) indicates that the property doesn't exist or can presume a default.

More importantly this is up to the ECMAScript specs to define, not Microsoft. If Microsoft implements their own version of JavaScript types... we are back in IE6 **** all over again.

I'm building an app that uses IndexedDB as a core component right now. The lack of visibility into the datastore means that I have to develop in another browser by default. I'd vote for this but I'm out of votes.

On December 15th of 2011 Microsoft made a big change that largely goes unnoticed by the vast majority of users; updates to Internet Explorer began to happen automatically.

Today, Microsoft continues to install the latest updates for Internet Explorer supported by the user’s operating system without getting in the way. With Internet Explorer 10 we also added a UI control to the “About Internet Explorer” window which gave the end-user easier control over this process.

Understandably there are some situations in which auto-updates are not desired. For instance, enterprise customers may (and do) choose to opt-out of these updates due to a reliance upon older versions of Internet Explorer internally.

Tasked with supporting legacy applications, while also supporting the advancing web, the Internet Explorer team developed Enterprise Mode for Internet Explorer 11. This feature is designed to grant the user all of the security and speed of a modern browser, while maintaining the integrity of legacy applications.

It is our expectation that Enterprise Mode will continue to liberate users from older versions of IE. This was yet another step towards our goal of bringing Windows users current. You can expect that we will continue to prioritize these efforts moving forward.

On December 15th of 2011 Microsoft made a big change that largely goes unnoticed by the vast majority of users; updates to Internet Explorer began to happen automatically.

Today, Microsoft continues to install the latest updates for Internet Explorer supported by the user’s operating system without getting in the way. With Internet Explorer 10 we also added a UI control to the “About Internet Explorer” window which gave the end-user easier control over this process.

Understandably there are some situations in which auto-updates are not desired. For instance, enterprise customers may (and do) choose to opt-out of these updates due to a reliance upon older versions of Internet Explorer internally.

Tasked with supporting legacy applications, while also supporting the advancing web, the Internet Explorer team developed Enterprise Mode for Internet Explorer 11. This feature is designed to grant the user all of the security and speed of a modern browser,…