Re: Separating Transclusion Mechanisms for Inheritance and Data Binding

2014-04-30 Thread Jan Miksovsky
I just saw Dimitri's reference to my “Filling slots in shadow” blog posts from a while back, so I thought I’d follow up with the experiences I’ve had I wrote it. First, I remain convinced that it will be very helpful for Shadow DOM to provide a feature like this that allows for parent and child

Re: Separating Transclusion Mechanisms for Inheritance and Data Binding

2014-04-28 Thread Dimitri Glazkov
Possibly relevant to the conversation: Jan Miksovsky (cc'd) had been thinking in this problem space for a while, and has a couple of great blog posts on the topic: http://blog.quickui.org/2013/11/08/filling-slots-in-shadow/ http://blog.quickui.org/2013/06/11/puzzle-define-html-custom-element-subc

Re: Separating Transclusion Mechanisms for Inheritance and Data Binding

2014-04-28 Thread Dimitri Glazkov
On Sun, Apr 27, 2014 at 2:36 PM, Ryosuke Niwa wrote: > On Apr 22, 2014, at 10:46 AM, Dimitri Glazkov > wrote: > > BTW, here's a jsbin that implements yield/transclude using existing Shadow > DOM plumbing: > > http://jsbin.com/pacim/1/edit > > > Thanks for an example. That indeed polyfills the A

Re: Separating Transclusion Mechanisms for Inheritance and Data Binding

2014-04-27 Thread Ryosuke Niwa
On Apr 22, 2014, at 10:46 AM, Dimitri Glazkov wrote: > BTW, here's a jsbin that implements yield/transclude using existing Shadow > DOM plumbing: > > http://jsbin.com/pacim/1/edit Thanks for an example. That indeed polyfills the API we're proposing in terms of the currently spec'ed API. On

Re: Separating Transclusion Mechanisms for Inheritance and Data Binding

2014-04-27 Thread Ryosuke Niwa
On Apr 22, 2014, at 10:13 AM, Dimitri Glazkov wrote: > On Thu, Apr 17, 2014 at 2:42 AM, Ryosuke Niwa wrote: > Review: Template Inheritance in the Current Specification > > In the current specification, a super class doesn't define any hooks for > subclasses. Instead, it defines insertion point

Re: Separating Transclusion Mechanisms for Inheritance and Data Binding

2014-04-27 Thread Ryosuke Niwa
ed from shadow element's children including > nodes inside content element. If we didn't have the content element inside > my-webkitten-card with "name" and "email" classes, then we would only see > WebKitten and kit...@webkit.org distributed into my-card's insertion p

Re: Separating Transclusion Mechanisms for Inheritance and Data Binding

2014-04-22 Thread Erik Bryn
*claps for sharing JSBin* Would love to see more of this on public-webapps when possible :) On Tue, Apr 22, 2014 at 10:46 AM, Dimitri Glazkov wrote: > BTW, here's a jsbin that implements yield/transclude using existing Shadow > DOM plumbing: > > http://jsbin.com/pacim/1/edit > > :DG< >

Re: Separating Transclusion Mechanisms for Inheritance and Data Binding

2014-04-22 Thread Dimitri Glazkov
Here's a jsbin that uses the shadow-as-function syntax and does the same thing: http://jsbin.com/peqoz/2/edit :DG< On Tue, Apr 22, 2014 at 10:46 AM, Dimitri Glazkov wrote: > BTW, here's a jsbin that implements yield/transclude using existing Shadow > DOM plumbing: > > http://jsbin.com/pacim/1/

Re: Separating Transclusion Mechanisms for Inheritance and Data Binding

2014-04-22 Thread Dimitri Glazkov
BTW, here's a jsbin that implements yield/transclude using existing Shadow DOM plumbing: http://jsbin.com/pacim/1/edit :DG<

Re: Separating Transclusion Mechanisms for Inheritance and Data Binding

2014-04-22 Thread Dimitri Glazkov
't have the content > element inside my-webkitten-card with "name" and "email" classes, then we > would only see WebKitten and kit...@webkit.org distributed into my-card's > insertion points as in: > > > > > > Name: > >

Re: Separating Transclusion Mechanisms for Inheritance and Data Binding

2014-04-22 Thread Dimitri Glazkov
On Thu, Apr 17, 2014 at 2:42 AM, Ryosuke Niwa wrote: > *Review: Template Inheritance in the Current Specification* > > In the current specification, a super class doesn't define any hooks for > subclasses. Instead, it defines insertion points into which nodes from the > original DOM ("light DOM"

Re: [Shadow DOM] Separating Transclusion Mechanisms for Inheritance and Data Binding

2014-04-21 Thread Ryosuke Niwa
On Apr 21, 2014, at 4:36 PM, William Chen wrote: > On 4/17/14, 2:42 AM, Ryosuke Niwa wrote: >> Review: Template Inheritance in the Current Specification >> >> In the current specification, a super class doesn't define any hooks for >> subclasses. Instead, it defines insertion points into which

Re: [Shadow DOM] Separating Transclusion Mechanisms for Inheritance and Data Binding

2014-04-21 Thread William Chen
On 4/17/14, 2:42 AM, Ryosuke Niwa wrote: > *Review: Template Inheritance in the Current Specification* > > In the current specification, a super class doesn't define any hooks > for subclasses. Instead, it defines insertion points into which nodes > from the original DOM ("light DOM") is inserted,

Re: [Shadow DOM] Separating Transclusion Mechanisms for Inheritance and Data Binding

2014-04-21 Thread Ryosuke Niwa
Ryosuke Niwa >>> >>> >>> Email: >>> >>> rn...@webkit.org >>> kit...@webkit.org >>> >>> >>> >>> >>> >>> >>> >>&g

Re: [Shadow DOM] Separating Transclusion Mechanisms for Inheritance and Data Binding

2014-04-20 Thread Hayato Ito
x27;t have the content > element inside my-webkitten-card with "name" and "email" classes, then we > would only see WebKitten and kit...@webkit.org distributed into my-card's > insertion points as in: > > > > > > Name: > >