direct_proxies "problem"

David Bruant bruant.d at gmail.com
Wed Jan 9 14:24:13 PST 2013


Le 09/01/2013 21:57, Andrea Giammarchi a écrit :
> Last, but not least, even offline DOM proxies are pointless, here 
> another example without putting them in the DOM
What's an "offline DOM Proxy"?

> var p = new Proxy(
>    document.createElement("p"),
>
>    {}
> );
> try {
>    p.appendChild(
That's what you call "without putting them in the DOM"? ;-)
What are you going to do when your proxy node has a child? Probably put 
it on the DOM eventually, I guess, no?

>      document.createElement("span")
>    );
> } catch(o_O) {
>    console.log(o_O.message);
> }
> try {
>    p.appendChild(
>      new Proxy(
>        document.createElement("span"),
>
>        {}
>      )
>    );
> } catch(o_O) {
>    console.log(o_O.message);
> }
> So, as it is right now, there is not a single reason to make them valid as new Proxy target, IMHO
Membrane and avoiding the cost of the shadow target sounds like a good 
enough.

David


More information about the es-discuss mailing list