W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

Re: [Shadow] URL-based shadows?

From: Dimitri Glazkov <dglazkov@google.com>
Date: Fri, 13 Mar 2015 10:44:12 -0700
Message-ID: <CADh5Ky0LeYHXcoh_hNqHUF=p=ZtWyG4BXaaxbSkhZ95HFc7zKA@mail.gmail.com>
To: Travis Leithead <travis.leithead@microsoft.com>
Cc: WebApps WG <public-webapps@w3.org>, "Anne van Kesteren (annevk@annevk.nl)" <annevk@annevk.nl>, Arron Eicholz <arronei@microsoft.com>, Elliott Sprehn <esprehn@google.com>
... found it:
https://docs.google.com/document/d/1V7ci1-lBTY6AJxgN99aCMwjZKCjKv1v3y_7WLtcgM00/edit?pli=1

:DG<

On Thu, Mar 12, 2015 at 6:05 PM, Dimitri Glazkov <dglazkov@google.com>
wrote:

> Yep. Elliott (cc'd) had a proposal like this a while back. It was coolly
> received (can't remember the details).
>
> :DG<
>
> On Thu, Mar 12, 2015 at 5:46 PM, Travis Leithead <
> travis.leithead@microsoft.com> wrote:
>
>>  Dimitri et al.,
>>
>>
>>
>>    Has the idea of loading/parsing a Shadow DOM directly from a URL been
>> discussed already? (e.g., a sort-of “micro-import” or an import that parses
>> its document directly into the ShadowRoot container?) I’m curious to know
>> if there’s some obvious flaw that I’m missing.
>>
>>
>>
>> element.createShadowRoot(“path to my component”);
>>
>>
>>
>>   This is an idea around building components from the “inside out”, and
>> using the URL as the basis for script-level access control to the Shadow
>> contents.
>>
>>
>>
>>   Thoughts?
>>
>
>
Received on Friday, 13 March 2015 17:44:38 UTC

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