slate-react 0.117.2 → 0.117.3

package/dist/index.js

@@ -796,7 +796,22 @@ function createAndroidInputManager(_ref) {
               insertPositionHint = false;
             }
             if (canStoreDiff) {
+              var currentSelection = editor.selection;
               storeDiff(_start.path, _diff);
+              if (currentSelection) {
+                var newPoint = {
+                  path: _start.path,
+                  offset: _start.offset + _text.length
+                };
+                scheduleAction(function () {
+                  slate.Transforms.select(editor, {
+                    anchor: newPoint,
+                    focus: newPoint
+                  });
+                }, {
+                  at: newPoint
+                });
+              }
               return;
             }
           }
@@ -4448,10 +4463,23 @@ var withReact = function withReact(editor) {
   e = slateDom.withDOM(e, clipboardFormatKey);
   var _e = e,
     onChange = _e.onChange,
-    apply = _e.apply;
+    apply = _e.apply,
+    insertText = _e.insertText;
   e.getChunkSize = function () {
     return null;
   };
+  if (slateDom.IS_ANDROID) {
+    e.insertText = function (text, options) {
+      // COMPAT: Android devices, specifically Samsung devices, experience cursor jumping.
+      // This issue occurs when the ⁠insertText function is called immediately after typing.
+      // The problem arises because typing schedules a selection change.
+      // However, this selection change is only executed after the ⁠insertText function.
+      // As a result, the already obsolete selection is applied, leading to incorrect
+      // final cursor position.
+      slateDom.EDITOR_TO_PENDING_SELECTION["delete"](e);
+      return insertText(text, options);
+    };
+  }
   e.onChange = function (options) {
     // COMPAT: React < 18 doesn't batch `setState` hook calls, which means
     // that the children and selection can get out of sync for one render