- From: <bugzilla@jessica.w3.org>
- Date: Thu, 27 Mar 2014 16:30:37 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24451 Eliot Graff <eliotgra@microsoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|eliotgra@microsoft.com |xn--mlform-iua@xn--mlform-i | |ua.no --- Comment #16 from Eliot Graff <eliotgra@microsoft.com> --- OK, hopefully, this will bring us to a single solution, even if we may generate three nodes of thinking* (*Sorry, geek humor) Anyway, I've rewritten the concluding sentences of the note so that the whole note now reads as follows. If this is acceptable, Leif, can you please close the bug. If you see the need for further edits, just let me know in the bug and reassign it to me and I'll take care of them right away. Thanks, gentlemen!! *********************************************** NOTE The statement that a "CDATA section must appear at the start of its containing element, and hence be the first child of that element," is due to how parsers may create DOM nodes based on characters and whitespace. The following script element, because it contains no whitespace outside the CDATA node, has one node, whether parsed as HTML or as XML: <script><![CDATA[foo]]>/<script> Because an author may need to comment out the CDATA "start tag" and "end tag," polyglot markup allows for one node before and after the CDATA section. The following example has three nodes: one text node before the CDATA section, one for the CDATA section, itself, and one after the CDATA section: Fig. 5 CDATA section that is commented out, resulting in a total of three DOM nodes. Example 12 <script>/*<![CDATA[*/ foo /*]]>*/</script> Thus, a CDATA section may appear at the beginning of its containing element, span the entire element, be the only node of the element, and yet still generate more than one DOM node. Polyglot markup therefore permits content that results in a single DOM node before and/or after the CDATA section. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 27 March 2014 16:30:39 UTC