diff options
author | Minteck <contact@minteck.org> | 2023-02-23 19:34:56 +0100 |
---|---|---|
committer | Minteck <contact@minteck.org> | 2023-02-23 19:34:56 +0100 |
commit | 3d1cd02f27518f1a04374c7c8320cd5d82ede6e9 (patch) | |
tree | 75be5fba4368472fb11c8015aee026b2b9a71888 /school/node_modules/w3c-xmlserializer/README.md | |
parent | 8cc1f13c17fa2fb5a4410542d39e650e02945634 (diff) | |
download | pluralconnect-3d1cd02f27518f1a04374c7c8320cd5d82ede6e9.tar.gz pluralconnect-3d1cd02f27518f1a04374c7c8320cd5d82ede6e9.tar.bz2 pluralconnect-3d1cd02f27518f1a04374c7c8320cd5d82ede6e9.zip |
Updated 40 files, added 37 files, deleted 1103 files and renamed 3905 files (automated)
Diffstat (limited to 'school/node_modules/w3c-xmlserializer/README.md')
-rw-r--r-- | school/node_modules/w3c-xmlserializer/README.md | 41 |
1 files changed, 0 insertions, 41 deletions
diff --git a/school/node_modules/w3c-xmlserializer/README.md b/school/node_modules/w3c-xmlserializer/README.md deleted file mode 100644 index da4790f..0000000 --- a/school/node_modules/w3c-xmlserializer/README.md +++ /dev/null @@ -1,41 +0,0 @@ -# w3c-xmlserializer - -An XML serializer that follows the [W3C specification](https://w3c.github.io/DOM-Parsing/). - -This package can be used in Node.js, as long as you feed it a DOM node, e.g. one produced by [jsdom](https://github.com/jsdom/jsdom). - -## Basic usage - -Assume you have a DOM tree rooted at a node `node`. In Node.js, you could create this using [jsdom](https://github.com/jsdom/jsdom) as follows: - -```js -const { JSDOM } = require("jsdom"); - -const { document } = new JSDOM().window; -const node = document.createElement("akomaNtoso"); -``` - -Then, you use this package as follows: - - -```js -const serialize = require("w3c-xmlserializer"); - -console.log(serialize(node)); -// => '<akomantoso xmlns="http://www.w3.org/1999/xhtml"></akomantoso>' -``` - -## `requireWellFormed` option - -By default the input DOM tree is not required to be "well-formed"; any given input will serialize to some output string. You can instead require well-formedness via - -```js -serialize(node, { requireWellFormed: true }); -``` - -which will cause `Error`s to be thrown when non-well-formed constructs are encountered. [Per the spec](https://w3c.github.io/DOM-Parsing/#dfn-require-well-formed), this largely is about imposing constraints on the names of elements, attributes, etc. - -As a point of reference, on the web platform: - -* The [`innerHTML` getter](https://w3c.github.io/DOM-Parsing/#dom-innerhtml-innerhtml) uses the require-well-formed mode, i.e. trying to get the `innerHTML` of non-well-formed subtrees will throw. -* The [`xhr.send()` method](https://xhr.spec.whatwg.org/#the-send()-method) does not require well-formedness, i.e. sending non-well-formed `Document`s will serialize and send them anyway. |