Create gh-pages branch via GitHub

This commit is contained in:
Wouter Scherphof 2013-04-05 11:05:57 -07:00
parent 4bac9dcb27
commit dc3817399f
2 changed files with 11 additions and 4 deletions

View File

@ -121,15 +121,22 @@ Now, find sepcific contained elements by selecting:</p>
<ul> <ul>
<li>Attribute values in selectors currently cannot contain any spaces, since space is interpreted as a delimiter between the <code>ancestor</code> and <code>descendant</code>, <code>parent</code> and <code>&gt;</code>, or <code>&gt;</code> and <code>child</code> parts of the selector</li> <li>Attribute values in selectors currently cannot contain any spaces, since space is interpreted as a delimiter between the <code>ancestor</code> and <code>descendant</code>, <code>parent</code> and <code>&gt;</code>, or <code>&gt;</code> and <code>child</code> parts of the selector</li>
<li>Likewise, for the <code>parent &gt; child</code> relation, the spaces before and after the <code>&gt;</code> are mandatory</li> <li>Consequently, for the <code>parent &gt; child</code> relation, the spaces before and after the <code>&gt;</code> are mandatory</li>
<li>Attribute values in selectors currently also cannot contain any of <code>#</code>, <code>.</code>, <code>[</code>, <code>]</code>, <code>:</code>, <code>(</code>, or <code>)</code>
</li>
<li> <li>
<code>&lt;!</code> elements are not parsed, including doctype, comments, and CDATA</li> <code>&lt;!</code> elements are not parsed, including doctype, comments, and CDATA</li>
<li>Textnodes are not seperate entries in the tree, so the content of <code>&lt;p&gt;line1&lt;br /&gt;line2&lt;/p&gt;</code> is plainly <code>"line1&lt;br /&gt;line2"</code> <li>Textnodes are not seperate entries in the tree, so the content of <code>&lt;p&gt;line1&lt;br /&gt;line2&lt;/p&gt;</code> is plainly <code>"line1&lt;br /&gt;line2"</code>
</li> </li>
<li>All start and end tags should be explicitly specified in the text to be parsed; omitted tags (as <a href="http://www.w3.org/TR/html5/syntax.html#optional-tags">permitted</a> by the the HTML spec) are NOT implied. Only the <a href="http://www.w3.org/TR/html5/syntax.html#void-elements">void</a> elements naturally don't need an end tag</li> <li>All start and end tags should be explicitly specified in the text to be parsed; omitted tags (as <a href="http://www.w3.org/TR/html5/syntax.html#optional-tags">permitted</a> by the the HTML spec) are NOT implied. Only the <a href="http://www.w3.org/TR/html5/syntax.html#void-elements">void</a> elements naturally don't need (and mustn't have) an end tag</li>
<li>The HTML text is not validated in any way; tag and attribute names and the nesting of different tags is completely arbitrary. The only HTML-specific part of the parser is that it knows which tags are void elements</li>
</ul><h2>Examples</h2> </ul><h2>Examples</h2>
<p>See <code>./doc/samples.lua</code></p> <p>See <code>./doc/sample.lua</code></p>
<h2>Tests</h2>
<p>See <code>./tst/init.lua</code></p>
<h2>Element type</h2> <h2>Element type</h2>

File diff suppressed because one or more lines are too long