On Tue, Jan 8, 2013 at 4:46 PM, David Bruant <[email protected]> wrote:
> > One idea would be in the short term that implementations reliably *always* > throw when trying to wrap non-ECMAScript objects and play with them as if > they were legit browser objects. If the need becomes strong, implementation > can later allow it (turning an error into a legit thing is usually not web > breaking) At least in V8/JSC for WebKit DOM objects are real ECMAScript objects. -- erik
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
