A DOM use case that can't be emulated with direct proxies

Brandon Benvie brandon at brandonbenvie.com
Wed Dec 12 15:17:28 PST 2012

Yeah I was using it in the Mozilla terminology way, not referring to the
browser. =D

On Wed, Dec 12, 2012 at 6:16 PM, Brendan Eich <brendan at mozilla.org> wrote:

> Brandon Benvie wrote:
>> The ability to break invariants of the language either requires an
>> external object-capability provider to dole out permission to do this (such
>> as what is currently done with "chrome" code
> Just to clarify for anyone following along (including me!), you must mean
> Firefox or another XUL app's UI "chrome" including privileged JS, which
> indeed is endowed with extra capabilities. Not Google Chrome -- right?
> /be
>  being executed with access to privileged internals), or a mechanism in
>> the language to dole out special permissions that goes beyond "first come,
>> first serve".
>> ______________________________**_________________
>> es-discuss mailing list
>> es-discuss at mozilla.org
>> https://mail.mozilla.org/**listinfo/es-discuss<https://mail.mozilla.org/listinfo/es-discuss>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20121212/b51fa2f4/attachment.html>

More information about the es-discuss mailing list