W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2015

Re: [components] Isolated Imports and Foreign Custom Elements

From: Anne van Kesteren <annevk@annevk.nl>
Date: Mon, 4 May 2015 11:24:56 +0200
Message-ID: <CADnb78h6_H-3kQLACHJUoL54n+kTe0nN_QCy-1OT2xTb8WAMtA@mail.gmail.com>
To: Maciej Stachowiak <mjs@apple.com>
Cc: WebApps WG <public-webapps@w3.org>
On Sat, May 2, 2015 at 12:07 AM, Maciej Stachowiak <mjs@apple.com> wrote:
> It’s already possible to run a constructor from another global object in the non-cross-origin case.

Okay, that makes more sense. I first read it as a suggestion we'd
construct a node using a same-global constructor and then also run the
foreign-global constructor and it didn't really compute.

> I think it may be necessary to do an experimental implementation to work out all the details of how the two-way isolation works.

I have the feeling there's some overlap with compartments:
http://andreasgal.com/2010/10/13/compartments/ Though I guess
non-Gecko implementations still want to avoid going there.

Another thing that might be nice is that if these elements are that
much isolated, perhaps we can consider allowing them to be renamed
them as well, similar to what module systems allow you to do.

Received on Monday, 4 May 2015 09:25:20 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:31 UTC