Tom Van Cutsem
tomvc.be at gmail.com
Wed Sep 26 12:49:06 PDT 2012
2012/9/26 David Bruant <bruant.d at gmail.com>
> With the current design, however, the DOM can figure out whether the end
> target of a proxy chain is a genuine DOM object and potentially accept it
> as Node in the DOM tree if that's what the end target is.
I can't tell whether it's a good or bad idea, whether it's worth the
> implementation cost, but the proxy design shift has re-opened that door.
I agree it's tempting, but it's a dangerous road in the sense that it might
pierce membranes (i.e. membranes having no place to stand when some
built-in method inadvertently reaches into the built-in target object and
exposes some object that it references). I'm not sure if there would be any
such case in e.g. the DOM, but if we go down this road, it may become an
issue in the future.
I agree we should strive to allow proxies in as much places as possible,
but I don't feel like the proxy design would be broken if there are a few
cases where this is not possible. Any system must eventually bottom out at
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss