W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > February 2012

[Bug 16153] New: [Templates]: Enable generated template elements to share a content docFrag

From: <bugzilla@jessica.w3.org>
Date: Tue, 28 Feb 2012 20:27:04 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-16153-2532@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16153

           Summary: [Templates]: Enable generated template elements to
                    share a content docFrag
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
        AssignedTo: dglazkov@chromium.org
        ReportedBy: rafaelw@chromium.org
         QAContact: public-webapps-bugzilla@w3.org


Clever templating use cases can optimize memory usage by sharing template
content.

e.g.

<template iterate="foo">
  <span>{{ Person }}</span>
  <template iterate="stuffInPocket">
     <span>{{ whatsInPocket }}</span>
  </template>
</template>

---

The templating library is likely to stamp out multiple copies of 

  <span>{{ Person }}</span>
  <template iterate="stuffInPocket">
     <span>{{ whatsInPocket }}</span>
  </template>

maybe there's some way that each instance doesn't have to have a generated
<template> element that contains exactly the same 

  <span>{{ whatsInPocket }}</span>

content docFrag

---

we could make content read-write, but then badness might occur if the content
is assigned a docFrag owned by the outer document.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 28 February 2012 20:27:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 28 February 2012 20:27:07 GMT