W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

[WebIDL] interface objects and properties too restrictive?

From: Travis Leithead <travil@microsoft.com>
Date: Tue, 3 Aug 2010 23:57:19 +0000
To: Cameron McCormack <cam@mcc.id.au>, "Sam Weinig (weinig@apple.com)" <weinig@apple.com>
CC: "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <9768D477C67135458BF978A45BCF9B3816FB86@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
Hey folks, just wondering what the justification behind the current {DontDelete} semantics are in WebIDL 4.4 [1] and 4.5 (second bullet) [2]. When our IE9 binding ported this to ES5, it translated to "configurable: false", which completely destroyed the ability to set accessors on the interface objects as well as operations (and in our case, DOM accessors). Because of this, we actually don't mark our interface objects OR operations/attributes as configurable: false, rather configurable: true.*

If this seems reasonable, I'd like to see the spec updated.


*special exceptions apply :-)

[1] http://dev.w3.org/cvsweb/~checkout~/2006/webapi/WebIDL/Overview.html?rev=1.206&content-type=text/html; charset=iso-8859-1#es-interfaces
[2] http://dev.w3.org/cvsweb/~checkout~/2006/webapi/WebIDL/Overview.html?rev=1.206&content-type=text/html; charset=iso-8859-1#host-objects
Received on Tuesday, 3 August 2010 23:57:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:10 UTC