- From: Domenic Denicola <domenic@domenicdenicola.com>
- Date: Wed, 2 Oct 2013 23:52:02 +0000
- To: Boris Zbarsky <bzbarsky@MIT.EDU>, Tab Atkins Jr. <jackalmage@gmail.com>
- CC: "public-script-coord@w3.org" <public-script-coord@w3.org>
From: Boris Zbarsky [mailto:bzbarsky@MIT.EDU] > On 10/2/13 5:42 PM, Tab Atkins Jr. wrote: >> It's doing that outside of ES, then. > Yes, of course. That's what the DOM implementation tends to do: work non-ES-accessible state! And this highlights the essential problem. As discussed ad naseum on es-discuss, it's impossible to make proxies work faithfully on objects that have private state. (The only solution is membranes, whose effects are much more far-reaching than make sense for this effort.) An attempt at some proxy-based solution will never work for DOM objects, full stop. Best to consider other approaches.
Received on Wednesday, 2 October 2013 23:52:33 UTC