Release 0.22.0

Work on ProseMirror has been somewhat slow lately, because I was focused on other work, but there have been some useful patches, so I figured I’d cut another release. No (intentional) breaking changes whatsoever this time. Enjoy!

Release notes

prosemirror-model 0.22.0 (2017-06-29)

Bug fixes

When using parseSlice, inline DOM content wrapped in block elements for which no parse rule is defined will now be properly wrapped in a textblock node.

New features

Resolved positions now have a doc accessor to easily get their root node.

Parse rules now support a namespace property to match XML namespaces.

The NodeRange constructor is now public (whereas before you could only construct these through blockRange).

prosemirror-transform 0.22.0 (2017-06-29)

Bug fixes

canSplit now returns false when given custom after-split node types that don’t match the content at that point.

Fixes canLift incorrectly returning null when lifting into an isolating node.

prosemirror-view 0.22.0 (2017-06-29)

Bug fixes

Fix an issue where moving the cursor through a text widget causes the editor to lose the selection in Chrome.

Fixes an issue where down-arrow in front of a widget would sometimes not cause any cursor motion on Chrome.

Destroying a mounted editor view no longer leaks event handlers.

Display updates for regular, non-composition input are now synchronous, which should reduce flickering when, for example, updating decorations in response to typing.

New features

The editor can now be initialized in a document other than the global document (say, an iframe).

Editor views now have a domAtPos method, which gives you the DOM position corresponding to a given document position.

prosemirror-inputrules 0.22.0 (2017-06-29)

Bug fixes

Input rules with spaces in them now match any whitespace where the space is expected, to avoid mysteriously not working when a non-breaking space is present.

5 Likes