Skip to content
Permalink
Browse files

[ac] (0) Hoist requirements on what text can consist of from the text…

…/html syntax to the DOM, so it also applies to XML and script-provided data.

Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=15557
Affected topics: HTML, HTML Syntax and Parsing

git-svn-id: http://svn.whatwg.org/webapps@6968 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Feb 6, 2012
1 parent 54f33ed commit 6c8b5f997c5154528479bcd6360b28dff7a75ae9
Showing with 60 additions and 31 deletions.
  1. +20 −10 complete.html
  2. +20 −10 index
  3. +20 −11 source
nodes are empty or contain just <a href=#space-character title="space character">space
characters</a>).</p>

<!--<p><code>Text</code> nodes and attribute values may begin with
an <i>isolated combining character</i>. <a
href="#refsUNICODE">[UNICODE]</a></p>--> <!-- commented out since
<p><code><a href=#text>Text</a></code> nodes and attribute values must consist of
<a href=#unicode-character title="Unicode character">Unicode characters</a>, must not
contain U+0000 characters, must not contain permanently undefined
Unicode characters (noncharacters), and must not contain control
characters other than <a href=#space-character title="space character">space
characters</a>.

<!--<code>Text</code> nodes and attribute values may begin with an
<i>isolated combining character</i>.--> <!-- commented out since
nothing disallows it currently, so it's implicit; however, if we
ever make charmod a normative reference, this will be needed to
override it -->

This specification includes extra constraints on the exact value of
<code><a href=#text>Text</a></code> nodes and attribute values depending on their
precise context.

<!-- <a href="#refsUNICODE">[UNICODE]</a>-->

</p>



<h6 id=embedded-content-0><span class=secno>3.2.5.1.6 </span>Embedded content</h6>
<h4 id=text-1><span class=secno>12.1.3 </span>Text</h4>

<p><dfn id=syntax-text title=syntax-text>Text</dfn> is allowed inside elements,
attribute values, and comments. Text must consist of <a href=#unicode-character title="Unicode character">Unicode characters</a>. Text must not
contain U+0000 characters. Text must not contain permanently
undefined Unicode characters (noncharacters). Text must not contain
control characters other than <a href=#space-character title="space character">space
characters</a>. Extra constraints are placed on what is and what
is not allowed in text based on where the text is to be put, as
described in the other sections.</p>
attribute values, and comments. Extra constraints are placed on what
is and what is not allowed in text based on where the text is to be
put, as described in the other sections.</p>


<h5 id=newlines><span class=secno>12.1.3.1 </span>Newlines</h5>
30 index
nodes are empty or contain just <a href=#space-character title="space character">space
characters</a>).</p>

<!--<p><code>Text</code> nodes and attribute values may begin with
an <i>isolated combining character</i>. <a
href="#refsUNICODE">[UNICODE]</a></p>--> <!-- commented out since
<p><code><a href=#text>Text</a></code> nodes and attribute values must consist of
<a href=#unicode-character title="Unicode character">Unicode characters</a>, must not
contain U+0000 characters, must not contain permanently undefined
Unicode characters (noncharacters), and must not contain control
characters other than <a href=#space-character title="space character">space
characters</a>.

<!--<code>Text</code> nodes and attribute values may begin with an
<i>isolated combining character</i>.--> <!-- commented out since
nothing disallows it currently, so it's implicit; however, if we
ever make charmod a normative reference, this will be needed to
override it -->

This specification includes extra constraints on the exact value of
<code><a href=#text>Text</a></code> nodes and attribute values depending on their
precise context.

<!-- <a href="#refsUNICODE">[UNICODE]</a>-->

</p>



<h6 id=embedded-content-0><span class=secno>3.2.5.1.6 </span>Embedded content</h6>
<h4 id=text-1><span class=secno>12.1.3 </span>Text</h4>

<p><dfn id=syntax-text title=syntax-text>Text</dfn> is allowed inside elements,
attribute values, and comments. Text must consist of <a href=#unicode-character title="Unicode character">Unicode characters</a>. Text must not
contain U+0000 characters. Text must not contain permanently
undefined Unicode characters (noncharacters). Text must not contain
control characters other than <a href=#space-character title="space character">space
characters</a>. Extra constraints are placed on what is and what
is not allowed in text based on where the text is to be put, as
described in the other sections.</p>
attribute values, and comments. Extra constraints are placed on what
is and what is not allowed in text based on where the text is to be
put, as described in the other sections.</p>


<h5 id=newlines><span class=secno>12.1.3.1 </span>Newlines</h5>
31 source
nodes are empty or contain just <span title="space character">space
characters</span>).</p>

<!--<p><code>Text</code> nodes and attribute values may begin with
an <i>isolated combining character</i>. <a
href="#refsUNICODE">[UNICODE]</a></p>--> <!-- commented out since
<p><code>Text</code> nodes and attribute values must consist of
<span title="Unicode character">Unicode characters</span>, must not
contain U+0000 characters, must not contain permanently undefined
Unicode characters (noncharacters), and must not contain control
characters other than <span title="space character">space
characters</span>.

<!--<code>Text</code> nodes and attribute values may begin with an
<i>isolated combining character</i>.--> <!-- commented out since
nothing disallows it currently, so it's implicit; however, if we
ever make charmod a normative reference, this will be needed to
override it -->

This specification includes extra constraints on the exact value of
<code>Text</code> nodes and attribute values depending on their
precise context.

<!-- <a href="#refsUNICODE">[UNICODE]</a>-->

</p>



<h6>Embedded content</h6>
<h4>Text</h4>

<p><dfn title="syntax-text">Text</dfn> is allowed inside elements,
attribute values, and comments. Text must consist of <span
title="Unicode character">Unicode characters</span>. Text must not
contain U+0000 characters. Text must not contain permanently
undefined Unicode characters (noncharacters). Text must not contain
control characters other than <span title="space character">space
characters</span>. Extra constraints are placed on what is and what
is not allowed in text based on where the text is to be put, as
described in the other sections.</p>
attribute values, and comments. Extra constraints are placed on what
is and what is not allowed in text based on where the text is to be
put, as described in the other sections.</p>


<h5>Newlines</h5>

0 comments on commit 6c8b5f9

Please sign in to comment.
You can’t perform that action at this time.