W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2009

Re: Conflicts between W3C specs and ES5?

From: Brendan Eich <brendan@mozilla.org>
Date: Sun, 15 Nov 2009 16:24:55 -0800
Cc: public-script-coord@w3.org
Message-Id: <748594F4-FDDE-456F-8055-69E94FE09962@mozilla.org>
To: "Mark S. Miller" <erights@google.com>
On Nov 15, 2009, at 2:45 PM, Mark S. Miller wrote:

> At the recent joint W3C / EcmaScript committee meeting, it was stated
> that the only known conflicts between HTML5 and related specs vs.
> EcmaScript 5 are
>  1) Is the global object the same as the object at the end of the
> scope chain? (HTML5: yes. ES5: no).

Rather, HTML5: no, the last object on the scope chain is not the same  
as the |this| value in global code; ES5: yes, they are the same.

The issue is best stated in terms of global code |this| binding since  
otherwise the object at the end of the scope chain and "the global  
object" are not obviously distinguishable.

>  2) What is document.all? (HTML5: a falsy host object. ES5: All
> objects (i.e., all non-primitive values) including all host objects
> are truthy.)
> Just now, by chance, I came across
> <http://wiki.whatwg.org/wiki/Web_ECMAScript> which enumerates other
> alleged conflicts. What is the status of that page?

Best to ask its maintainers, who may not all be on public-script- 
coord, but it looks like more potential over-specification, or (in the  
best possible light) informative material on existing browser JS  
differences, which should help standards bodies to avoid over- 
specifying normative behavior.

Received on Monday, 16 November 2009 00:25:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:01 UTC