- From: Brendan Eich <brendan@mozilla.com>
- Date: Fri, 25 Sep 2009 23:32:55 -0700
- To: Yehuda Katz <wycats@gmail.com>
- Cc: public-webapps@w3.org, Doug Schepers <schepers@w3.org>, HTML WG <public-html@w3.org>, es-discuss Steen <es-discuss@mozilla.org>
On Sep 25, 2009, at 11:28 PM, Brendan Eich wrote: > We seem to agree, perhaps vehemently :-/. > > One last time, for the record: it is a bug in ES specs that you > can't follow th Sorry, rogue cut before send. "it's a bug in ES specs that you can't follow them in order to implement a web-compatible JS engine." Although some of "web-compatible JS" really does belong in W3C specs, not ES specs, it's clear ES1 pretending there is only one global object did no one any favors. Ditto for execution model and (ultimately) split windows, as Hixie pointed out in raising the conflict between HTML5 and ES1-3 (and now ES5). Just wanted to reassure you, since you seemed to think otherwise, that no one views it as a feature that ES specs don't specify enough. HTML4 specs didn't either. We're getting there. /be > The whole point of bothering the HTML WG, public-webapps, and es- > discuss about collaboration between Ecma and W3C folks has been to > fill gaps between specs and reality. We had some false starts in my > view (like trying to move ES WebIDL bindings to Ecma up front, or > ever). But the issues laid out in Sam's original cross-post were > exactly the "gaps" between ES specs, HTML5 ones, and browser > implementations. At last some of the gaps are filled in HTML5 but > not in ways that can be injected directly into ES specs. > > We should fix the ES specs, and make whatever changes follow to the > HTML5 specs. And maybe use WebIDL to constrain "host objects". All > this has been said on the thread already. Were you not reading the > messages I was? > > /be > > _______________________________________________ > es-discuss mailing list > es-discuss@mozilla.org > https://mail.mozilla.org/listinfo/es-discuss
Received on Saturday, 26 September 2009 06:33:47 UTC