@codemirror/view 6.2.1 → 6.2.2

package/CHANGELOG.md

@@ -1,3 +1,9 @@
+## 6.2.2 (2022-08-31)
+
+### Bug fixes
+
+Don't reset the selection for selection change events that were suppressed by a node view.
+
 ## 6.2.1 (2022-08-25)
 
 ### Bug fixes

package/dist/index.cjs

@@ -5562,14 +5562,18 @@ class DOMObserver {
         }
     }
     onSelectionChange(event) {
+        let wasChanged = this.selectionChanged;
         if (!this.readSelectionRange() || this.delayedAndroidKey)
             return;
         let { view } = this, sel = this.selectionRange;
         if (view.state.facet(editable) ? view.root.activeElement != this.dom : !hasSelection(view.dom, sel))
             return;
         let context = sel.anchorNode && view.docView.nearest(sel.anchorNode);
-        if (context && context.ignoreEvent(event))
+        if (context && context.ignoreEvent(event)) {
+            if (!wasChanged)
+                this.selectionChanged = false;
             return;
+        }
         // Deletions on IE11 fire their events in the wrong order, giving
         // us a selection change event before the DOM changes are
         // reported.
@@ -6900,6 +6904,11 @@ the editor's vertical layout structure. The ones provided as
 functions are called _after_ the new viewport has been computed,
 and thus **must not** introduce block widgets or replacing
 decorations that cover line breaks.
+
+If you want decorated ranges to behave like atomic units for
+cursor motion and deletion purposes, also provide the range set
+containing the decorations to
+[`EditorView.atomicRanges`](https://codemirror.net/6/docs/ref/#view.EditorView^atomicRanges).
 */
 EditorView.decorations = decorations;
 /**

package/dist/index.d.ts

@@ -1054,6 +1054,11 @@ declare class EditorView {
     functions are called _after_ the new viewport has been computed,
     and thus **must not** introduce block widgets or replacing
     decorations that cover line breaks.
+    
+    If you want decorated ranges to behave like atomic units for
+    cursor motion and deletion purposes, also provide the range set
+    containing the decorations to
+    [`EditorView.atomicRanges`](https://codemirror.net/6/docs/ref/#view.EditorView^atomicRanges).
     */
     static decorations: Facet<DecorationSet | ((view: EditorView) => DecorationSet), readonly (DecorationSet | ((view: EditorView) => DecorationSet))[]>;
     /**

package/dist/index.js

@@ -5555,14 +5555,18 @@ class DOMObserver {
         }
     }
     onSelectionChange(event) {
+        let wasChanged = this.selectionChanged;
         if (!this.readSelectionRange() || this.delayedAndroidKey)
             return;
         let { view } = this, sel = this.selectionRange;
         if (view.state.facet(editable) ? view.root.activeElement != this.dom : !hasSelection(view.dom, sel))
             return;
         let context = sel.anchorNode && view.docView.nearest(sel.anchorNode);
-        if (context && context.ignoreEvent(event))
+        if (context && context.ignoreEvent(event)) {
+            if (!wasChanged)
+                this.selectionChanged = false;
             return;
+        }
         // Deletions on IE11 fire their events in the wrong order, giving
         // us a selection change event before the DOM changes are
         // reported.
@@ -6893,6 +6897,11 @@ the editor's vertical layout structure. The ones provided as
 functions are called _after_ the new viewport has been computed,
 and thus **must not** introduce block widgets or replacing
 decorations that cover line breaks.
+
+If you want decorated ranges to behave like atomic units for
+cursor motion and deletion purposes, also provide the range set
+containing the decorations to
+[`EditorView.atomicRanges`](https://codemirror.net/6/docs/ref/#view.EditorView^atomicRanges).
 */
 EditorView.decorations = decorations;
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codemirror/view",
-  "version": "6.2.1",
+  "version": "6.2.2",
   "description": "DOM view component for the CodeMirror code editor",
   "scripts": {
     "test": "cm-runtests",