@signal9/era-ui 24.0.2 → 24.0.3

package/CHANGELOG.md

@@ -1,3 +1,9 @@
+## [24.0.3](https://github.com/sig-nine/era-ui/compare/v24.0.2...v24.0.3) (2026-08-12)
+
+### Bug Fixes
+
+* **pane:** the focused pane's second hairline was a shadow, not the outline ([0d44f17](https://github.com/sig-nine/era-ui/commit/0d44f17cb7d2fee11fb5eea72b8cd674be9036ef))
+
 ## [24.0.2](https://github.com/sig-nine/era-ui/compare/v24.0.1...v24.0.2) (2026-08-11)
 
 ### Bug Fixes

package/dist/os/pane.svelte

@@ -92,7 +92,20 @@
 		// border-(--color-7) rather than `border-7`, which Tailwind reads as a 7px
 		// border WIDTH — the numeric colour scale collides with the width scale on
 		// border-*, so it always takes the paren-var form here.
-		focused ? 'border-(--color-7)' : 'opacity-95 shadow-sm',
+		// shadow-sm on BOTH states, so the only thing focus changes is the border's
+		// colour (and the recede opacity). It used to sit only on the unfocused
+		// branch, leaving the focused pane on Pane.Root's `shadow-lg` — and since
+		// flat's --era-shadow-lg became a 1px hairline ring (so floating panels
+		// could be told apart from the page), a focused pane drew that ring ON TOP
+		// OF its own 1px border. Two hairlines, reported as "the border grows and
+		// thickens when a pane is focused".
+		//
+		// An elevation step is the right focus signal on glass and bevel and is
+		// impossible on flat, which has no depth by construction — there, more
+		// shadow can only mean another line. So the shadow is held constant and
+		// focus is carried by colour, which reads on all three.
+		'shadow-sm',
+		focused ? 'border-(--color-7)' : 'opacity-95',
 		pane.state === 'minimized' && 'hidden'
 	)}
 >

package/dist/ui/pane/pane-root.svelte

@@ -514,14 +514,17 @@
 		// same way rd-xs was inside rd-sm before the handle moved up a tier.
 		// A hairline edge, because a floating pane is the one thing that must be
 		// separable from whatever is behind it — and on the FLAT surface it had
-		// nothing to do it with: --era-shadow-lg collapses to none there, so the
-		// pane's whole edge was a tone step from the desktop. The reference terminal
+		// nothing to do it with: --era-shadow-lg collapsed to none there, so the
+		// pane's whole edge was a tone step from the desktop. (Flat's shadow-lg is
+		// a hairline ring now — f329475 — which is why the pane must NOT also take
+		// it: a border plus that ring is two lines, and that is what a focused pane
+		// used to render.) The reference terminal
 		// app draws this as a real 1px border, and that border is also why its
 		// chrome reads as having more air: a border consumes a pixel of the box, so
 		// everything inside starts a pixel further in. Same token'd hairline the
 		// bubble toolbar uses, so it tracks the surface instead of being a drawn-on
-		// line. When focused, the outline below lands on it at -1px and takes over,
-		// which is that app's border-6 -> border-8 in era's idiom.
+		// line. Focus recolours THIS border — that app's border-6 -> border-8 in
+		// era's idiom — rather than drawing anything additional.
 		// contain:layout style — a moving pane must not make the page re-solve
 		// layout it cannot have affected. NOT `size` (the pane auto-sizes to its
 		// content until the grip sets a size, and size containment would collapse

package/package.json

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