summaryrefslogtreecommitdiff
path: root/alarm/node_modules/w3c-xmlserializer/README.md
diff options
context:
space:
mode:
authorMinteck <contact@minteck.org>2023-01-10 14:54:04 +0100
committerMinteck <contact@minteck.org>2023-01-10 14:54:04 +0100
commit99c1d9af689e5325f3cf535c4007b3aeb8325229 (patch)
treee663b3c2ebdbd67c818ac0c5147f0ce1d2463cda /alarm/node_modules/w3c-xmlserializer/README.md
parent9871b03912fc28ad38b4037ebf26a78aa937baba (diff)
downloadpluralconnect-99c1d9af689e5325f3cf535c4007b3aeb8325229.tar.gz
pluralconnect-99c1d9af689e5325f3cf535c4007b3aeb8325229.tar.bz2
pluralconnect-99c1d9af689e5325f3cf535c4007b3aeb8325229.zip
Update - This is an automated commit
Diffstat (limited to 'alarm/node_modules/w3c-xmlserializer/README.md')
-rw-r--r--alarm/node_modules/w3c-xmlserializer/README.md41
1 files changed, 0 insertions, 41 deletions
diff --git a/alarm/node_modules/w3c-xmlserializer/README.md b/alarm/node_modules/w3c-xmlserializer/README.md
deleted file mode 100644
index da4790f..0000000
--- a/alarm/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.