- From: Maciej Stachowiak <mjs@apple.com>
- Date: Tue, 12 Aug 2008 19:52:41 -0700
- To: Travis Leithead <travil@windows.microsoft.com>
- Cc: Web Applications Working Group WG <public-webapps@w3.org>, "cam@mcc.id.au" <cam@mcc.id.au>, Allen Wirfs-Brock <Allen.Wirfs-Brock@microsoft.com>, "Pratap Lakshman (VJ#SDK)" <pratapl@microsoft.com>
On Aug 12, 2008, at 8:31 AM, Travis Leithead wrote: > > Cameron, > > I recently became aware of Microsoft's involvement in the ECMAScript > 3.1 effort as of about a month ago. (Including Allen & Pratap from > MS Jscript, who are driving that effort.) ES3.1 makes a few subtle > changes that I thought you'd like to follow up on, since they impact > the WebIDL spec, namely "DontDelete" is changing to "Flexible", > among other things which should be noted in WebIDL. > > I've also done some recent investigation on how browsers handle > ECMAScript's operators (delete, new, instanceof, etc.) and found > that they are somewhat diverging in implementation; in particular > the 'delete' operator. I've noted that some implementations use the > delete operator in the DOM in the same spirit that it is speced in > ECMAScript--that is the delete operator removes a given property > completely. I've noted that other implementations only allow the > delete operator to remove a "shadowed" property on the DOM, but > never actual delete the underlying "built-in" property. I wondered > if WebIDL makes any mention of the behavior of ECMAScript operators > on host objects and how they should behave? Since ECMAScript 3.0 is still the operative standard and the future plans for ECMAScript have been unclear and may change markedly in the future, I would advise against making this change at present. Regards, Maciej
Received on Wednesday, 13 August 2008 02:53:22 UTC