@plannotator/ui 0.46.0 → 0.46.1

package/HANDOFF.md

@@ -1527,6 +1527,7 @@ The guide chain's engine plumbing (Claude/Codex/marker commands, output parsing,
 
 ## Publishing & versioning
 
+- **ui 0.46.1 (fix, ui only, core pin unchanged at `0.25.6`):** `useVimSelection` (mounted by every `Viewer`) now only clears a page selection whose anchor or focus lies inside the viewer's own container; with vim off it used to clear the WHOLE page's selection on every mount and `contentVersion` change, so a selection in another host panel vanished whenever the document behind it loaded or changed.
 - **ui 0.45.0 (annotation card header slot + mentions on the card's edit box): `@plannotator/ui` only — `@plannotator/core` is UNCHANGED at `0.25.5`, so this publishes alone** (core 0.25.5 must already be published). Purely additive over 0.44.0, both props on `AnnotationPanel`: `renderCardHeader` (the header-row twin of `renderCardFooter`, wrapper `[data-annotation-card-header]`, renders under `readOnly`, open-document cards only in the All-files view) and `mentionSource` (the 0.43.0 type, applied to the card's EDIT box, saving `onEdit(id, { text, mentions })` only when a source was supplied and a pick survived). Nothing is removed, no new supported imports (`components/MentionAutocomplete` is internal glue), no export-, share- or archive-visible change, and Plannotator passes neither — `packages/editor` and `packages/review-editor` have zero source diff, and the panel is byte-identical to 0.44.0. Known difference from `CommentPopover`: no chips in the card's edit box (follow-up named in the section). See "Annotation card header slot and mentions on the edit box (0.45.0)".
 - **ui 0.44.0 (mention token chips in the composer): `@plannotator/ui` only — `@plannotator/core` is UNCHANGED at `0.25.5`, so this publishes alone** (core 0.25.5 must already be published). Purely additive over 0.43.2: the `@Label` tokens a `mentionSource` composer inserted render as chips in the composer's existing highlight overlay, `MentionSource.tokenClassName?` lets a host restyle them (under the metric rule), `useMentionAutocomplete` also returns the surviving `mentions`, and `utils/composerTokens` joins the supported-import list. Nothing is removed, no export-, share- or archive-visible change, and Plannotator passes none of it — with neither `mentionSource` nor `skillReferences` the composer is byte-identical to 0.43.2. See "Mention token chips in the composer (0.44.0)".
 - **ui 0.43.1 (`mentionSource` on the viewers): `@plannotator/ui` only — `@plannotator/core` is UNCHANGED at `0.25.5`, so this publishes alone** (core 0.25.5 must already be published). Purely additive over 0.43.0: `mentionSource` on `Viewer` and `HtmlViewer` (forwarded to every comment composer each mounts) and the optional `Annotation.mentions` field the picked ids land on, set only when a source was supplied and a token survived. Nothing is removed, no new modules, no export-, share- or archive-visible change, and Plannotator passes none of it. See "`mentionSource` on the viewers (0.43.1)".
@@ -1548,7 +1549,7 @@ The guide chain's engine plumbing (Claude/Codex/marker commands, output parsing,
 
 ---
 
-## `Settings` `annotateParity` (unreleased, after 0.46.0)
+## `Settings` `annotateParity` (shipped in 0.46.0)
 
 `<Settings mode="annotate">` takes a new optional `annotateParity?: boolean`,
 default `false`. **A host that omits it sees exactly the annotate Settings it

package/README.md

@@ -367,7 +367,7 @@ npm install @plannotator/ui @plannotator/core
 - `@plannotator/core` — pure utils + types, zero deps, browser-safe (CI enforces no `node:` imports). Published.
 - `@plannotator/ui` — React components/hooks + theme + `configure()`. Depends on an exact published `@plannotator/core` version. Published.
 - `@plannotator/shared`, `@plannotator/ai` — stay private to the monorepo; `shared` re-exports `core`'s modules via shims so Plannotator's internals are untouched.
-- Currently `@plannotator/ui` 0.46.0 depends exactly on `@plannotator/core` 0.25.6. `core` is bumped only when something under `packages/core` changes, so `ui` can advance alone. Keep the published core version exact in `packages/ui/package.json`; do not use a `workspace:` protocol there, because a directly published manifest must remain installable outside this monorepo. Bun still links the matching local workspace during development. When both packages change, publish `core` first, then build and publish the UI tarball. See HANDOFF.md "Publishing & versioning" for the verification command.
+- Currently `@plannotator/ui` 0.46.1 depends exactly on `@plannotator/core` 0.25.6. `core` is bumped only when something under `packages/core` changes, so `ui` can advance alone. Keep the published core version exact in `packages/ui/package.json`; do not use a `workspace:` protocol there, because a directly published manifest must remain installable outside this monorepo. Bun still links the matching local workspace during development. When both packages change, publish `core` first, then build and publish the UI tarball. See HANDOFF.md "Publishing & versioning" for the verification command.
 
 ## The one rule
 

package/hooks/useVimSelection.ts

@@ -227,6 +227,27 @@ function applyVisualBlockSelection(
   if (points) applyNativeTextSelection(graph.container, points.cursor, points.anchor);
 }
 
+/**
+ * Clear the page selection only when it touches the viewer's own document.
+ *
+ * A page has ONE selection, so an unconditional `removeAllRanges()` also kills
+ * a selection the user just made somewhere else (another panel of a host app,
+ * the annotation sidebar). A selection belongs to the viewer when its anchor or
+ * focus lies inside the container; with no container nothing is cleared.
+ */
+function clearSelectionWithin(container: HTMLElement | null | undefined): void {
+  if (!container) return;
+  const selection = window.getSelection();
+  if (!selection || selection.rangeCount === 0) return;
+  const { anchorNode, focusNode } = selection;
+  if (
+    (anchorNode && container.contains(anchorNode))
+    || (focusNode && container.contains(focusNode))
+  ) {
+    selection.removeAllRanges();
+  }
+}
+
 /**
  * Own semantic block navigation and precise text selection while the rendered
  * document has focus.
@@ -291,7 +312,7 @@ export function useVimSelection({
     if (!initial) return null;
     const next: VimBlockState = { phase: 'block', targetKey: initial.key };
     setState(next);
-    window.getSelection()?.removeAllRanges();
+    clearSelectionWithin(container);
     scrollVimTargetIntoView(initial.element, scrollViewportRef.current);
     return next;
   }, [containerRef, setState]);
@@ -302,7 +323,7 @@ export function useVimSelection({
       setFocused(false);
       setHelpOpen(false);
       setHudCommand(null);
-      window.getSelection()?.removeAllRanges();
+      clearSelectionWithin(containerRef.current);
       return;
     }
     if (!focused) return;
@@ -366,9 +387,9 @@ export function useVimSelection({
 
   const setSemanticTarget = useCallback((target: SemanticTarget) => {
     setState(semanticStateForTarget(target));
-    window.getSelection()?.removeAllRanges();
+    clearSelectionWithin(containerRef.current);
     scrollVimTargetIntoView(target.element, scrollViewportRef.current);
-  }, [setState]);
+  }, [containerRef, setState]);
 
   const updateTextState = useCallback((
     graph: SemanticTargetGraph,
@@ -816,13 +837,13 @@ export function useVimSelection({
           setSemanticTarget(parent);
         } else {
           setState(createInitialVimSelectionState());
-          window.getSelection()?.removeAllRanges();
+          clearSelectionWithin(graph.container);
         }
         return;
       }
       case 'block':
         setState(createInitialVimSelectionState());
-        window.getSelection()?.removeAllRanges();
+        clearSelectionWithin(graph.container);
     }
   }, [setSemanticTarget, setState, updateTextState]);
 
@@ -1041,7 +1062,7 @@ export function useVimSelection({
   const onMouseDown = useCallback((event: ReactMouseEvent<HTMLElement>) => {
     if (!enabled || isDocumentKeyboardControl(event.target)) return;
     setState(createInitialVimSelectionState());
-    window.getSelection()?.removeAllRanges();
+    clearSelectionWithin(event.currentTarget);
     if (document.activeElement !== event.currentTarget) {
       pointerFocusRef.current = true;
       event.currentTarget.focus({ preventScroll: true });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plannotator/ui",
-  "version": "0.46.0",
+  "version": "0.46.1",
   "type": "module",
   "exports": {
     "./components/*": "./components/*.tsx",