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.
-Travis
*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
