Internet Explorer - How IE9 Platform Preview Feedback Changed the JavaScript Standard

[AWS]

When we first introduced our plans for Internet Explorer Platform Previews we said that &ldquodevelopers and people interested in standards and web development can try out new platform functionality and provide early feedback.&rdquo We are now getting such feedback on a daily basis and are using it to improve IE9. However, sometimes the impact of the feedback extends beyond just IE9. Here is the story of how some recent feedback regarding the third IE9 Platform Preview resulted in a correction to the new ECMAScript 5th Edition (ES5) standard for JavaScript.

 

 

The ES5 standard became official in December 2009 and the third IE9 Platform Preview is the first widely distributed implementation of some subtle details of the ES5 specification. ES5 was designed to be highly compatible with existing websites and the Ecma International TC39 technical committee worked to avoid any non-security related changes that might break existing JavaScript code. However, perfection generally does not exist in the world of software so with the third IE9 Platform Preview we were very interested to see if any ES5-related compatibility problems with existing sites would show up.

 

 

Soon after releasing this platform preview, we received reports that some web-apps that use the jQuery framework did not work correctly in the preview. We tracked the problem to a specific jQuery API method that in some cases passed a caller provided value to Object.prototype.toString without first checking if the value was null or undefined. Specifically, some calls to this jQuery method:

 

isFunction: function( obj ) {

return toString.call(obj) === "[object Function]"

},

 

 

 

failed with an exception: &ldquoTypeError: Object expected&rdquo. Further analysis showed that toString in the above code was the built-in method Object.prototpe.toString and that the failures occurred when isFunction was being called with undefined as its argument. Why does an exception occur in IE9 and not in previous versions of IE or other browsers? It is because the third IE9 Platform Preview in standards mode actually conforms to the ES5 specification for Object.prototype.toString.

 

 

According to the prior editions of the ECMAScript specification, calling any built-in method using null or undefined as the this value passes the &ldquoglobal object&rdquo (in browsers this is the DOM window object) to the method as its this value.