Re: [Shadow] URL-based shadows?

2015-03-18 Thread Ryosuke Niwa
> On Mar 18, 2015, at 4:08 PM, Travis Leithead > wrote: > >> From: Ryosuke Niwa [mailto:rn...@apple.com] >> I think this idea resonates well with the cross-origin use case / API change >> proposal we made two years ago [1]. In that proposal, we went a step >> further and tied custom elements

RE: [Shadow] URL-based shadows?

2015-03-18 Thread Travis Leithead
> From: Ryosuke Niwa [mailto:rn...@apple.com] >I think this idea resonates well with the cross-origin use case / API change >proposal we made two years ago [1].  In that proposal, we went a step further >and tied custom elements with URLs so that those shadow DOM can be >automatically instantiat

Re: [Shadow] URL-based shadows?

2015-03-18 Thread Dimitri Glazkov
On Wed, Mar 18, 2015 at 2:35 PM, Travis Leithead < travis.leith...@microsoft.com> wrote: > I think ‘Worker’ threw me off at first J. > > > > My original use case was to make the current model of loading components > more “local”, as AFAIK, these components can only presently be loaded by > code y

Minuts IndieUI Teleconference 18 March 2015

2015-03-18 Thread Michael Cooper
http://www.w3.org/2015/03/18-indie-ui-minutes.html

RE: [Shadow] URL-based shadows?

2015-03-18 Thread Travis Leithead
I think ‘Worker’ threw me off at first ☺. My original use case was to make the current model of loading components more “local”, as AFAIK, these components can only presently be loaded by code you trust, e.g., via some script library somewhere imported via a

Re: template namespace attribute proposal

2015-03-18 Thread Ryosuke Niwa
> On Mar 18, 2015, at 2:19 PM, Tab Atkins Jr. wrote: > > On Wed, Mar 18, 2015 at 2:06 PM, Ryosuke Niwa wrote: >> On Mar 16, 2015, at 3:14 PM, Tab Atkins Jr. wrote: >>> Karl Dubost said: The intersection seems to be: ['a', 'style', 'script', 'track', 'title', 'canvas', 'source', 'vide

Re: [Shadow] URL-based shadows?

2015-03-18 Thread Ryosuke Niwa
> On Mar 12, 2015, at 5:46 PM, Travis Leithead > wrote: > >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 >

Re: template namespace attribute proposal

2015-03-18 Thread Tab Atkins Jr.
On Wed, Mar 18, 2015 at 2:06 PM, Ryosuke Niwa wrote: > On Mar 16, 2015, at 3:14 PM, Tab Atkins Jr. wrote: >> Karl Dubost said: >>> The intersection seems to be: >>> ['a', 'style', 'script', 'track', 'title', 'canvas', 'source', 'video', >>> 'iframe', 'audio', 'font'] >> >> Whoops, sorry, forgot

Re: template namespace attribute proposal

2015-03-18 Thread Ryosuke Niwa
> On Mar 16, 2015, at 3:14 PM, Tab Atkins Jr. wrote: > > [Sorry for the reply-chain breaking; Gmail is being super weird about > your message in particular, and won't let me reply directly to it. > Some bug.] > > Karl Dubost said: >> The intersection seems to be: >> ['a', 'style', 'script', 'tr