[Harmony Proxies] Non-extensible, sealed and frozen Proxies

[Mark S. Miller]

On Wed, Sep 7, 2011 at 7:10 AM, Tom Van Cutsem <tomvc.be at gmail.com> wrote:

> 2011/9/7 David Bruant <david.bruant at labri.fr>
>
>> **
>> Le 07/09/2011 15:38, Tom Van Cutsem a écrit :
>>
>> [...]
>>
>>
>>  I still don't see how it would work out for NodeList or other host
>> objects. Then again, I don't know whether there is a use case that requires
>> this.
>>
>> Emulating the DOM, probably. It would still be possible to have
>> non-extensible trapping proxies, but not turn the proxy into a native DOM
>> Document/Node/Element/HTMLElement/DocumentFragment, etc... This could create
>> some bad performance penalty for DOM Traversers [1] for instance (or
>> querySelectorAll). Would it even be possible to have an "hybrid" DOM tree
>> with native DOM Node and emulated DOM Node?
>>
>
> So a sealed/frozen DOM element requires no more interposition at all?
>

I don't understand the question or how you got there.

Certainly, for security purposes, sealed/frozen DOM nodes still carry
tremendous authority, and so we still need to interpose proxy-wrappers for
them.

>
> Also, how straightforward would it be to brain-transplant a Proxy with,
> say, a NodeList, as opposed to brain-transplanting a Proxy with a regular
> Object?
>



-- 
    Cheers,
    --MarkM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20110907/20f7eb03/attachment.html>