On Tue, Aug 3, 2010 at 4:57 PM, Travis Leithead <[email protected]> wrote: > 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.
Sorry, I'm not very updated on the differences between the ES3 and ES5 worlds. Why does "configurable: false" destroyed the ability to set accessors? Can you give an example of a piece of script that doesn't work but which you'd like to work, and what you'd like it to do? / Jonas
