On Tue, Mar 12, 2013 at 10:20 PM, Dominic Cooney <[email protected]>wrote:
> On Tue, Mar 12, 2013 at 8:13 AM, Dimitri Glazkov <[email protected]>wrote: > >> Hi folks! >> >> Just had a quick discussion with Elliott and he suggested that instead of >> building full-blown Documents, the <link rel="components"> just make >> DocumentFragments, just like <template> does. >> > > I am confused by what you are proposing here. > > Templates "produce" document fragments in the sense that the > HTMLTemplateElement's content attribute is a DocumentFragment. > > On the other hand, templates use full-blown documents in the sense that > "the template contents owner is a document which does not have a browsing > context." < > https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/templates/index.html#definitions > > > > >> Looking at >> http://www.whatwg.org/specs/web-apps/current-work/multipage/dom.html#the-document-object >> and >> the bunch of APIs that will never be useful on a document without a >> browsing context, I think it's a pretty good idea. It should make also >> components more lightweight. >> > > It you are proposing to make the Component interface's content attribute a > DocumentFragment, I think that is OK. It does not make the components any > lighter, because component.content.ownerDocument will inevitably point to > that other document. > > Could you provide a more specific proposal? I don't understand what you're > proposing here. > Just like in HTML templates, you don't have to have a distinct document for each component. They could share the same document. In fact, it might be nice for both templates and components to all share the same document. :DG<
