pugixml/docs
Arseny Kapoulkine f49d7acdfb Clarify the document element behavior.
pugixml currently unconditionally accepts documents with multiple
top-level element nodes in absence of parse_fragment. This is an
unfortunate omission; while it can be corrected, it will result in
regressions for some users, and it's trivial to perform the validity
check after the parse is done.

Because of this, for now we're just going to amend documentation here to
both highlight this in the W3C Conformance section, but also to more
strongly push users into realizing that there's just a single document
element (normally).

We might decide to change the behavior here to prohibit such documents
by default in the future, but for now a documentation change seems like
a better tradeoff.

Fixes #337
2020-05-02 09:47:34 -07:00
..
images docs: Fix a typo in dom_tree.png 2017-12-29 17:03:54 -08:00
samples Fix whitespace issues 2016-01-24 14:05:44 +01:00
config.adoc Update all URLs to pugixml.org to https:// 2018-11-12 12:28:54 -08:00
manual.adoc Clarify the document element behavior. 2020-05-02 09:47:34 -07:00
manual.html docs: Update documentation for 1.10 release 2019-09-11 21:51:02 -07:00
quickstart.adoc docs: Draw attention to the fact that you have to compile pugixml.cpp 2019-01-19 18:25:25 -08:00
quickstart.html docs: Update documentation for 1.10 release 2019-09-11 21:51:02 -07:00