Releases: ianstormtaylor/slate
[email protected]
Patch Changes
- #5971
addf0c51Thanks @nabbydude! - Removed the last traces of immer and eliminated it as a dependency
[email protected]
Minor Changes
- #5968
49f28e50Thanks @TyMick! - Scroll to focus point of expanded selections indefaultScrollSelectionIntoView
Patch Changes
-
#5976
3d38db8fThanks @semimikoh! - Fix slate-dom peer dependency to require >=0.119.0 to resolve containsShadowAware import error -
#5975
d0d192b8Thanks @nabbydude! - Allow onValueChange and onSelectionChange to trigger on the same frame, fixing a few bugs where one was not being called
[email protected]
[email protected]
[email protected]
Patch Changes
-
#5957
bd66bfa2Thanks @scrapooo! - Fix:onValueChangewas not triggered when replacing text after selecting it from right to left. -
#5965
cc5a9d8cThanks @hiteshshetty-dev! - Ignores composition events when fired from nested input or textarea -
#5959
622fb115Thanks @hiteshshetty-dev! - Adds translate='no' to Editable component to skip DOM from translation
[email protected]
Patch Changes
-
#5929
fdaa9c80Thanks @12joan! - - Fix error when a non-selectable node has no next or previous node- Do not return points from
Editor.positionsthat are inside non-selectable nodes- Previously,
editor.isSelectablewas handled incorrectly insideEditor.positions. When encountering a non-selectable node, it would immediately return the point before or after it (depending onreverse), but it would not skip returning points inside the non-selectable node if more than one point was consumed fromEditor.positions.
- Previously,
- Do not return points from
-
#5943
aaad6717Thanks @12joan! - Fix: Thesplit: trueoption onTransforms.wrapNodesdoes not work correctly when one or more points is at the start or end of a text node. -
#5926
cf10119aThanks @12joan! - Use generics for the return type ofNode.fragment
[email protected]
[email protected]
Minor Changes
- #5923
ba33735aThanks @12joan! - - When removing a text node containing the cursor, always perfer placing the cursor in a sibling text node if one exists.- Previously, the selection would enter a sibling inline in some circumstances, even when a sibling text node was available.
- The most noticeable effect of this change occurs when pressing backspace at the start of line N when the last non-empty node in line N-1 is an inline.
- Before, the cursor would be placed inside the inline.
- Now, the cursor is placed outside the inline.