Domenic's https://github.com/domenic/window-proxy-spec seems headed in the right direction. I suggest starting there.
Test proposals by self-hosting in ES6. Such self hosting would use direct proxies *not* because the term "proxy" in WindowProxy has any historical relation -- it does not -- but because the rest of ES6 is not powerful enough to self-host its behavior. On Wed, Jan 14, 2015 at 5:56 PM, Bjoern Hoehrmann <[email protected]> wrote: > * Boris Zbarsky wrote: > >You say "every WindowProxy", but in practice in an ES implementation you > >have some object, it has some internal methods. This is the last time > >I'm bothering to go through this with you, since clearly we're getting > >nowhere, as I said in > https://www.w3.org/Bugs/Public/show_bug.cgi?id=27128 > > What are the odds that the behavior observable by web pages can actually > be defined sanely such that ES invariants and compatibility requirements > are satisfied? https://www.w3.org/Bugs/Public/show_bug.cgi?id=27128#c15 > indicates, as I understand it, the odds may be quite good. In that case, > looking for a volunteer to come up with a proposal might be a good next > step. > -- > Björn Höhrmann · mailto:[email protected] · http://bjoern.hoehrmann.de > D-10243 Berlin · PGP Pub. KeyID: 0xA4357E78 · http://www.bjoernsworld.de > Available for hire in Berlin (early 2015) · http://www.websitedev.de/ > -- Cheers, --MarkM
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
