mirror of
https://github.com/msva/lua-htmlparser.git
synced 2024-11-04 23:34:20 +00:00
Listed some more limitations
This commit is contained in:
parent
ee2dbcc557
commit
b58383affe
@ -69,8 +69,9 @@ Selectors can be combined; e.g. `".class:not([attribute]) element.class"`
|
|||||||
###Limitations
|
###Limitations
|
||||||
- Attribute values in selectors currently cannot contain any spaces, since space is interpreted as a delimiter between the `ancestor` and `descendant`, `parent` and `>`, or `>` and `child` parts of the selector
|
- Attribute values in selectors currently cannot contain any spaces, since space is interpreted as a delimiter between the `ancestor` and `descendant`, `parent` and `>`, or `>` and `child` parts of the selector
|
||||||
- Likewise, for the `parent > child` relation, the spaces before and after the `>` are mandatory
|
- Likewise, for the `parent > child` relation, the spaces before and after the `>` are mandatory
|
||||||
- `<!` elements are not parsed, including doctype and comments
|
- `<!` elements are not parsed, including doctype, comments, and CDATA
|
||||||
- Textnodes are not seperate entries in the tree, so the content of `<p>line1<br />line2</p>` is plainly `"line1<br />line2"`
|
- Textnodes are not seperate entries in the tree, so the content of `<p>line1<br />line2</p>` is plainly `"line1<br />line2"`
|
||||||
|
- All start and end tags should be explicitly specified in the text to be parsed; omitted tags (as [permitted](http://www.w3.org/TR/html5/syntax.html#optional-tags) by the the HTML spec) are NOT implied. Only the [void](http://www.w3.org/TR/html5/syntax.html#void-elements) elements naturally don't need an end tag
|
||||||
|
|
||||||
##Examples
|
##Examples
|
||||||
See `./doc/samples.lua`
|
See `./doc/samples.lua`
|
||||||
|
Loading…
Reference in New Issue
Block a user