Merge pull request #164 from oleksandr-danylchenko/fix-checking-null-elements-annotability

⚠️ Fixed checking `null` selection `anchorNode` for being `not-annotatable` ⚠️

Author: rsimon

packages/text-annotator/src/SelectionHandler.ts

@@ -75,6 +75,19 @@ export const SelectionHandler = (
   const onSelectionChange = debounce((evt: Event) => {
     const sel = document.getSelection();
 
+    /**
+     * In iOS when a user clicks on a button, the `selectionchange` event is fired.
+     * However, the generated selection is empty and the `anchorNode` is `null`.
+     * That doesn't give us information about whether the selection is in the annotatable area
+     * or whether the previously selected text was dismissed.
+     * Therefore - we should bail out from such a range processing.
+     *
+     * @see https://github.com/recogito/text-annotator-js/pull/164#issuecomment-2416961473
+     */
+    if (!sel?.anchorNode) {
+      return;
+    }
+
     /**
      * This is to handle cases where the selection is "hijacked"
      * by another element in a not-annotatable area.
@@ -189,7 +202,7 @@ export const SelectionHandler = (
         const currentIds = new Set(selected.map(s => s.id));
         const nextIds = Array.isArray(hovered) ? hovered.map(a => a.id) : [hovered.id];
 
-        const hasChanged = 
+        const hasChanged =
           currentIds.size !== nextIds.length ||
           !nextIds.every(id => currentIds.has(id));