prosemirror-view
Advanced tools
Changelog
0.17.4 (2017-02-02)
Fixes bug where widget decorations would sometimes get parsed as content when editing near them.
The editor now prevents the behavior of Ctrl-d and Ctrl-h on textblock boundaries on OS X, as intended.
Make sure long words don't cause a horizontal scrollbar in Firefox
Various behavior fixes for IE11.
Changelog
0.17.3 (2017-01-19)
DOM changes deleting a node's inner wrapping DOM element (for example the <code>
tag in a schema-basic code block) no longer break the editor.
Changelog
0.17.2 (2017-01-16)
Call custom click handlers before applying select-node behavior for a ctrl/cmd-click.
Fix failure to apply DOM changes that start at document position 0.
Changelog
0.17.1 (2017-01-07)
Fix issue where a document update that left the selection in the same place sometimes led to an incorrect DOM selection.
Make sure EditorView.focus
doesn't cause the browser to scroll the top of the editor into view.
Changelog
0.17.0 (2017-01-05)
The handleDOMEvent
prop has been dropped in favor of the handleDOMEvents
(plural) prop.
The onChange
prop has been replaced by a dispatchTransaction
prop (which takes a transaction instead of an action).
Added support for a handleDOMEvents
prop, which allows you to provide handler functions per DOM event, and works even for events that the editor doesn't normally add a handler for.
Add view method dispatch
, which provides a convenient way to dispatch transactions.
The dispatchTransaction
(used to be onAction
) prop is now optional, and will default to simply applying the transaction to the current view state.
Widget decorations now accept an option associative
which can be used to configure on which side of content inserted at their position they end up.
Typing immediately after deleting text now preserves the marks of the deleted text.
Transactions that update the selection because of mouse or touch input now get a metadata property pointer
with the value true
.
Changelog
0.16.0 (2016-12-23)
Solve problem where setting a node selection would trigger a DOM read, leading to the selection being reset.
Changelog
0.15.2 (2016-12-10)
The native selection is now appropriately hidden when there is a node selection.