RE: Browsers and ECMAscript editions

The other related issue is where E4X (ECMA-357) comes in...


From: [] On Behalf Of Oliver Hunt
Sent: Monday, July 12, 2010 1:08 PM
To: Chris Lilley
Cc: SVG Working Group WG
Subject: Re: Browsers and ECMAscript editions

Broadly speaking all of the major browsers are moving towards support for ES5, however much like HTML5 support comes in gradually over time -- a number of engines supported features that became part of ES5 years ago, some features have are supported only in the most recent releases, and some features are still some way off.

That said from the PoV of a spec there isn't a substantial change in language semantics between ES3 and ES5, the only real difference is the change in property attribute terminology:
ES3           ES5
DontEnum      enumerable
ReadOnly      writable
DontDelete    configurable

The basic difference is that the meanings are reversed, eg. DontEnum == !enumerable

But even these terms i think only really matter to the WebIDL spec -- the WebIDL spec provides the wrapper that most DOM related specs seem to use in defining behaviour.


On Jul 12, 2010, at 9:50 AM, Chris Lilley wrote:

On Monday, July 12, 2010, 4:19:06 PM, Chris wrote:

CL> Hello,

CL> Mohamed has asked us to link to ECMAScript 5th Edition of
CL> December 2009. We aren't sure what edition is actually implemented
CL> in browsers, and other SVG implementors.

CL> Comments by implementors would help here.

Mozilla  seems to be proceeding with ECMAScript 5th edition (1.5)

Webkit also

Opera has partial support and 'will support it once finalized'

Its not clear whether Mozilla Rhino
and thus other engines which use Rhino, such as Batik
are on ECMAScript 5.

A bugzilla bug indicates that it is requested, and may be underway

CL> ISSUE-2344

Chris Lilley          
Technical Director, Interaction Domain
W3C Graphics Activity Lead
Co-Chair, W3C Hypertext CG

Received on Monday, 12 July 2010 17:48:42 UTC