Issue #51

FIX: Fix an issue where an inner node's mark information could reset the
same mark provided by an outer node in the DOM parser.

Co-authored-by: lastnigtic <[email protected]>

FIX: Fix issue where 1.11.1 uses an array method not available on Internet Explorer.

FEATURE: The output of `toDOM` functions can now be a `{dom, contentDOM}`
object specifying the precise parent and content DOM elements.

See https://discuss.prosemirror.net/t/contentdom-when-returning-a-dom-node-from-todom/3209

Issue ProseMirror/prosemirror#1108

See https://discuss.prosemirror.net/t/underline-parserule-that-excludes-links/3302/9
See https://github.com/ProseMirror/rfcs/blob/master/text/0011-nonconsuming-parse-rules.md

FEATURE: Parse rules can now have a `consuming: false` property which
allows other rules to match their tag or style even when they apply.

See https://discuss.prosemirror.net/t/i-doubt-there-is-a-typo/3355

… type

FIX: Fix a bug where nested marks of the same type would be applied to
the wrong node when parsing from DOM.

See https://discuss.prosemirror.net/t/css-styles-as-marks-vs-decorations/3452/3

FIX: `MarkType.removeFromSet` now removes all instances of the mark, not just
the first one.

Issue ProseMirror/prosemirror-transform#17

FIX: Fix an issue where nested tags that match mark parser rules could cause
the parser to apply marks in invalid places.

Closes ProseMirror/prosemirror#1130

FEATURE: `Fragment.textBetween` is now public.

FIX: `Node.check` will now error if a node has an invalid combination of marks.

Closes ProseMirror/prosemirror#1116

Even when preserveWhitespace is "full".

FIX: Don't leave carriage return characters in parsed DOM content, since
they confuse Chrome's cursor motion.

Issue ProseMirror/prosemirror#1138

Issue ProseMirror/prosemirror#1148

…pace is full

FIX: DOM parsing with `preserveWhitespace: "full"` will no longer ignore
whitespace-only nodes.

Issue ProseMirror/prosemirror#1159

FIX: Be less agressive about dropping whitespace when the context isn't
know in `DOMParser.parseSlice`.

Issue ProseMirror/prosemirror#1182

FIX: `DOMSerializer.serializeNode` will no longer ignore the node's marks.

FEATURE: `textBetween` now allows its leaf text argument to be a function.

Issue ProseMirror/prosemirror#1228

FEATURE: A new `NodeSpec` property, `whitespace`, allows more control
over the way whitespace in the content of the node is parsed.

Issue ProseMirror/prosemirror-view#115

FIX: Fix a bug in the way whitespace-preservation options were handled
in `DOMParser`.

Issue ProseMirror/prosemirror#1248

See https://discuss.prosemirror.net/t/node-descendants-doc-update-request/4572

To avoid having our local Node type renamed to Node by the .d.ts bundler.

FIX: Fix a crash in DOM parsing.

See https://discuss.prosemirror.net/t/parse-issue-with-closeparent-option-enabled/4636

FEATURE: Node specs for leaf nodes now support a property `leafText` which, when given,
will be used by `textContent` and `textBetween` to serialize the node.

... allowing the statically known names of mark and node types to be accessed without error even with the TypeScript option `noUncheckedIndexedAccess` enabled. In addition, this should also make the node and mark types available for auto-completion in the editor. See https://discuss.prosemirror.net/t/prosemirror-is-now-a-typescript-project/4624/34 (#67)

FEATURE: Add optional type parameters to `Schema` for the node and mark names.

Since TypeScript somehow puts any in the .d.ts otherwise.

Issue ProseMirror/prosemirror#1283

Issue ProseMirror/prosemirror-view#129

FIX: Upgrade to orderedmap 2.0.0 to avoid around a TypeScript compilation issue.

This method will throw a RangeError with some debugging information
if the content is not valid.

Previously, it could also return 0

Discussion there works poorly, and it's started to attract spam. Use the
forum instead.

FIX: Improve DOM parsing of nested block elements mixing block and inline children.

Closes ProseMirror/prosemirror#1332

FIX: Copy all properties from the input spec to `Schema.spec`.

See https://discuss.prosemirror.net/t/attaching-custom-props-to-schemas-spec/5036

FEATURE: Parse rules for styles can now provide a `clearMark` property
to remove pending marks (for example for `font-style: normal`).

Issue ProseMirror/prosemirror#1347

FIX: Fix the types of `Fragment.desendants` to include the index parameter to the callback.

FIX: Include CommonJS type declarations in the package to please new
TypeScript resolution settings.

FIX: Allow parse rules with a `clearMark` directive to clear marks that have already
been applied.

Closes ProseMirror/prosemirror#1376

FIX: Don't apply style parse rules for nodes that are skipped by other parse rules.

Closes ProseMirror/prosemirror#1398

FIX: Make `textBetween` emit block separators for empty textblocks.

Closes ProseMirror/prosemirror#1419

FEATURE: The `ParseRule` type is now a union of `TagParseRule` and
`StyleParseRule`, with more specific types being used when
appropriate.

FEATURE: The new `linebreakReplacement` property on node specs makes it
possible to configure a node type that `setBlockType` will convert to and
from line breaks when appropriate.

Issue ProseMirror/prosemirror#1460

FIX: Improve performance and accuracy of `DOMParser` style matching by using
the DOM's own `style` object.

Issue ProseMirror/prosemirror#1470

Issue ProseMirror/prosemirror#1470

FIX: Make sure resolved positions (and thus the document and schema hanging
off them) don't get kept in the cache when their document can be garbage-collected.

Closes #81