On Thu, Aug 1, 2013 at 5:09 PM, Allen Wirfs-Brock <[email protected]> wrote: > In sounds like the actual intent is the Document and Window must be exotic > objects (ES6-speak) that do caller origin filtering on all MOP operations > applied to them. Presumably that is what the FF proxies implement.
I think HTML does special casing for Document/Window. Gecko is more complicated. See this simple demonstration: http://dump.testsuite.org/js/documentdomain.htm > This whole discussion and the related > https://www.w3.org/Bugs/Public/show_bug.cgi?id=20567 "change [[Prototype]]" > thread sure feel like Wack-A-Mole exercises. > > It sounds like we don't actually have a complete/understandable/rational > model of how the Document/Window rooted object model is supposed to behave > as a data structure shared among Realms/processes/host domains, etc. It > isn't even clear to me whether that level of direct sharing is actually > needed (except for compatibility issues). It's basically compatibility issues, as I understand it. The other problem is that there's generally great reluctance with respect to cleanup in addition to it being low priority. > Is it feasible to reboot the design and then go back and see what > compatibility shims need to be put in front of a new model. > > Unless something like that is done I fear that Wack-a-Mole will continue > forever without anything actually getting better. -- http://annevankesteren.nl/ _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
