@danxbot/ui 6.4.5 → 6.4.6

package/dist/types/lib/markdown/caret-map.d.ts

@@ -46,3 +46,24 @@ export declare function graphemeBefore(map: CaretMap, offset: number): Span | nu
 export declare function graphemeAfter(map: CaretMap, offset: number): Span | null;
 /** The first legal offset on the line holding `offset` — where Home goes. */
 export declare function lineStartStop(map: CaretMap, offset: number): number;
+/**
+ * The last legal offset on the line holding `offset` — where End goes.
+ *
+ * SG-799 — NOT SAFE TO LEAVE TO THE BROWSER, the way `input.ts` leaves
+ * vertical movement and word-wise movement to it. A block's own leading
+ * markup (`# `, `- `, `> `) renders as `display: inline-block; width: 0`
+ * (`styles/markdown.css`'s "markup is collapsed at all times" rule) so it can
+ * be reached at all without ever having visible geometry — but a zero-size
+ * `inline-block` is an ATOMIC box for Chromium's own line-navigation, and a
+ * real Chromium probe caught it landing End's selection INSIDE that leading
+ * box (`("# ", offset 2)`, the same on-screen point as where the caret
+ * already stood) instead of at the true end of the visible text — every time,
+ * on every block with a leading marker, regardless of heading level and
+ * regardless of whether the line was the document's last one. Home already
+ * had the model-side half of this fix (`lineStartStop`, above) sitting
+ * unused — nothing in `input.ts` ever called it, so Home had the identical
+ * exposure and simply hadn't been caught yet. Both are now computed here and
+ * written directly, the same way `moveCaret` already computes ArrowLeft/Right
+ * instead of trusting the browser.
+ */
+export declare function lineEndStop(map: CaretMap, offset: number): number;

package/dist/types/lib/markdown/surface.d.ts

@@ -130,6 +130,18 @@ export declare class MarkdownSurface {
      * source characters makes the caret appear to stall.
      */
     moveCaret(direction: 1 | -1, extend: boolean): boolean;
+    /**
+     * Moves the caret to the start or end of its current line, in the model,
+     * and writes the result. Home and End both have to be computed here rather
+     * than left to the browser — SG-799 — because a block's leading markup
+     * renders as a zero-size `inline-block` (`styles/markdown.css`), which
+     * Chromium treats as an atomic box for its own native line navigation, and
+     * a real Chromium probe caught End landing the browser's OWN selection
+     * inside that leading box instead of at the true end of the line.
+     *
+     * Returns false when there is no selection to move, matching `moveCaret`.
+     */
+    moveToLineEdge(edge: "start" | "end", extend: boolean): boolean;
     /**
      * Detects the third caret rule's failure: our own write left the browser's
      * selection somewhere that is no longer a position in this document.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@danxbot/ui",
-  "version": "6.4.5",
+  "version": "6.4.6",
   "type": "module",
   "description": "Danxbot — a domain-agnostic React design system with motion as a first-class primitive.",
   "license": "MIT",