@signal9/era-ui 4.16.1 → 4.16.3

package/dist/apps/notes/note-editor.svelte

@@ -209,6 +209,23 @@
 		text-box-edge: cap alphabetic;
 	}
 
+	/* The optical half of the trim. cap trimming is EXACT — the cap sits on the
+	 * container inset to the pixel — but the LEFT side isn't: glyphs start with
+	 * their side bearing (~0.07em of ink-free space inside the line box), so a
+	 * geometrically-equal corner read top-tight. The first block gets that same
+	 * allowance back as margin, in em so a heading's compensation scales with
+	 * the heading — the corner then MEASURES slightly uneven and finally LOOKS
+	 * even, which is the order optics always wins in.
+	 *
+	 * 0.15em, not the ~0.07em side-bearing alone: a first line is usually a
+	 * heavy cap or a heading, and dense ink right at a boundary needs more
+	 * room than a light vertical stem to feel equally far from it — the same
+	 * reason display type sets its top margin above geometric equality. Tuned
+	 * by eye against the left inset. */
+	.era-notes-prose :global(.tiptap > :first-child) {
+		margin-top: 0.15em;
+	}
+
 	/* FALLBACK for engines without text-box (Firefox): the trim above silently
 	 * disappears there, and the first line opened ~0.47em too low (measured:
 	 * cap 16.4px from the top against 8px from the left, dense/mono) — the
@@ -225,7 +242,9 @@
 	 * this block and keep the exact version. */
 	@supports not ((text-box-trim: trim-start) and (text-box-edge: cap alphabetic)) {
 		.era-notes-prose :global(.tiptap > :first-child) {
-			margin-top: -0.45em;
+			/* -0.45em of untrimmed leading, plus the same +0.15em optical
+			 * allowance the trimmed path adds above. */
+			margin-top: -0.3em;
 		}
 	}
 

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@signal9/era-ui",
-	"version": "4.16.1",
+	"version": "4.16.3",
 	"scripts": {
 		"dev": "vite dev --host",
 		"build": "vite build && npm run prepack",