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

[Bug 16280] [Templates]: Non-normative: Clarify the behavior of DOM traversal & serialize/deserialize APIS on template element

From: <bugzilla@jessica.w3.org>
Date: Thu, 16 Aug 2012 17:37:31 +0000
Message-Id: <E1T240h-0002pY-ES@jessica.w3.org>
To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16280

--- Comment #2 from Rafael Weinstein <rafaelw@chromium.org> 2012-08-16 17:37:31 UTC ---
[editorial]

So my feeling is that the tricky part of this is that given that a template
deserializes by lifting elements into its content DF, it stands to reason that
the reverse would be true. E.g. It seems desireable to retain the following:



document.documentElement.innerHTML = myMarkupString;
var output = document.documentElement.innerHTML;
assert(output == myMarkupString).

This suggests to me that template.innerHTML should parse the markup using
implied context parsing, and
replace its content DF with the resulting DOM.

---

I think that childNodes, appendChild, etc... should not delegate to the content
DF. E.g. though would behave much like <script> by simply appending children to
the template, but not affecting its content.

Serializing a <template> which both direct children and content would result
similarly to <script>. E.g.

<script>var i = 1;</script>

var i = document.getElementById('foo');
var div = i.appendChild(document.createElement('div'));
div.innerHTML = 'bar';
i.innerHTML // var i = 1;<div>bar</div>

-- 
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 Thursday, 16 August 2012 17:37:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 16 August 2012 17:37:32 GMT