On Sun, May 17, 2015 at 1:54 AM, Maciej Stachowiak wrote:
>
> (Replying to slightly old thread.)
>
> >
> > 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 al
(Replying to slightly old thread.)
>
> 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.
An earlier version of my proposal had support for arbit
7;m not sure to what extent your two-way membrane proxy would handle this
case...
-Original Message-
From: Maciej Stachowiak [mailto:m...@apple.com]
Sent: Friday, May 1, 2015 2:57 PM
To: Travis Leithead
Cc: Anne van Kesteren; WebApps WG
Subject: Re: [components] Isolated Imports and F
On Sat, May 2, 2015 at 12:07 AM, Maciej Stachowiak 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 t
On May 1, 2015, at 4:35 PM, Domenic Denicola wrote:
>> alert(weirdArray.__proto__ == localArray.__proto__)
>
> This alerts false in IE, Firefox, and Chrome.
>
That is what I'd expect it to do. (It does the same in Safari).
I guess I didn't explain why I put this line in, so for clarity: thi
> alert(weirdArray.__proto__ == localArray.__proto__)
This alerts false in IE, Firefox, and Chrome.
> On May 1, 2015, at 9:47 AM, Anne van Kesteren wrote:
>
> On Thu, Apr 23, 2015 at 8:58 PM, Maciej Stachowiak wrote:
>> I wrote up a proposal (with input and advice from Ryosuke Niwa) on a
>> possible way to extend Web Components to support fully isolated components:
>>
>> https://github.com/w
nts).
>
> Just some food for thought.
>
> [1]
> https://github.com/w3c/webcomponents/wiki/Cross-Origin-Custom-Elements:-Concept-and-Proposal
>
> -Original Message-
> From: Anne van Kesteren [mailto:ann...@annevk.nl]
> Sent: Friday, May 1, 2015 9:48 AM
> To:
com/w3c/webcomponents/wiki/Cross-Origin-Custom-Elements:-Concept-and-Proposal
-Original Message-
From: Anne van Kesteren [mailto:ann...@annevk.nl]
Sent: Friday, May 1, 2015 9:48 AM
To: Maciej Stachowiak
Cc: WebApps WG
Subject: Re: [components] Isolated Imports and Foreign Custom Elements
On Thu, Apr 23, 2015 at 8:58 PM, Maciej Stachowiak wrote:
> I wrote up a proposal (with input and advice from Ryosuke Niwa) on a
> possible way to extend Web Components to support fully isolated components:
>
> https://github.com/w3c/webcomponents/wiki/Isolated-Imports-Proposal
>
> I welcome comme
On Thu Apr 23 02:58 PM, Maciej Stachowiak wrote:
>
> https://github.com/w3c/webcomponents/wiki/Isolated-Imports-Proposal
>
> I welcome comments on whether this approach makes sense.
Security rules are unclear but love this approach
https://lists.w3.org/Archives/Public/public-webapps/2014JulSep/0
11 matches
Mail list logo
