@codemirror/view
Advanced tools
Changelog
6.26.3 (2024-04-12)
Fix an issue where dispatching an update to an editor before it measured itself for the first time could cause the scroll position to incorrectly move.
Fix a crash when multiple tooltips with arrows are shown.
Changelog
6.26.2 (2024-04-09)
Improve behavior of scrollPastEnd
in a scaled editor.
When available, use Selection.getComposedRanges
on Safari to find the selection inside a shadow DOM.
Remove the workaround that avoided inappropriate styling on composed text after a decoration again, since it breaks the stock Android virtual keyboard.
Changelog
6.26.1 (2024-03-28)
Fix the editor getting stuck in composition when Safari fails to fire a compositionend event for a dead key composition.
Fix an issue where, with IME systems that kept the cursor at the start of the composed text, the editor misidentified the target node and disrupted composition.
Fix a bug where in a line-wrapped editor, with some content, the initial scroll position would be off from the top of the document.
Changelog
6.26.0 (2024-03-14)
Avoid the editor getting confused when iOS autocorrects on pressing Enter and does the correction and the break insertion in two different events.
Fix the pasting of copied URIs in iOS.
Fix a bug where a scaled editor could keep performing unnecessary updates due to tiny differences in geometry values returned by the browser.
Fix a bug where, on iOS with a physical keyboard, the modifiers for some keys weren't being passed to the keymaps.
Work around the fact that Mobile Safari makes DOM changes before firing a key event when typing ctrl-d on an external keyboard.
Fix an issue where some commands didn't properly scroll the cursor into view on Mobile Safari.
Re-measure the document when print settings are changed on Chrome.
The EditorView.scrollHandler
facet can be used to override or extend the behavior of the editor when things are scrolled into view.
Changelog
6.25.1 (2024-03-06)
Fix accidental non-optional field in layer config objects.
Changelog
6.25.0 (2024-03-04)
Properly recognize Android GBoard enter presses that strip a space at the end of the line as enter.
Fix a bug that caused the gutter to have the wrong height when the editor was scaled after construction.
When starting a composition after a non-inclusive mark decoration, temporarily insert a widget that prevents the composed text from inheriting that mark's styles.
Make sure the selection is repositioned when a transaction changes decorations without changing the document.
View plugins can now provide a docViewUpdate
method that is called whenever the document view is updated.
Layers now take a updateOnDocUpdate
option that controls whether they are automatically updated when the document view changes.
Changelog
6.24.1 (2024-02-19)
Fix a crash that happens when hover tooltips are active during changes, introduced in 6.24.0.
Changelog
6.24.0 (2024-02-09)
Fix an issue that broke context-menu select-all on Chrome when the viewport didn't cover the whole document.
Make sure tooltips are ordered by extension precedence in the DOM.
Hover tooltip sources may now return multiple tooltips.
Changelog
6.23.1 (2024-01-24)
Fix a bug that caused Tooltip.above
to not take effect for tooltips that were already present when the tooltip plugin is initialized.
Automatically reposition tooltips when their size changes.
Changelog
6.23.0 (2023-12-28)
Work around odd iOS Safari behavior when doing select all.
Fix a composition interruption when an widget is inserted next to the cursor.
Fix a crash in bidirectional cursor motion.
Simplify visual motion through bidirectional text, fix several corner cases where it would work badly.
Fix a bug that broke some bidi isolates not on the first line of the document.
EditorView.bidiIsolatedRanges
now supports automatically determining the direction of the range if not provided by the decoration.
EditorView.visualLineSide
can be used to find the visual end or start of a line with bidirectional text.
The new EditorView.outerDecorations
facet can be used to provide decorations that should always be at the bottom of the precedence stack.