@kerfjs/ui 4.5.0-beta.1 → 5.0.0-beta.100

package/dist/styles/list.css

@@ -1,6 +1,22 @@
 .kui-list {
-  --kui-list-divider-color: var(--kui-color-border);
+  --kui-list-divider-color: var(--kui-color-neutral-border-normal);
   --kui-list-gap: var(--kui-layout-item-gap, 0.5rem);
+  /* Private per-instance values are reset on every List so a nested List that
+     omits `gap` or `flex` never inherits its ancestor's; the component's inline
+     style overrides these defaults for the props it does set. */
+  --_kui-list-gap: 0;
+  --_kui-list-column-gap: var(--_kui-list-gap);
+  --_kui-list-row-gap: var(--_kui-list-gap);
+  --_kui-list-flex: 0 1 auto;
+  --_kui-list-inset-top: 0px;
+  --_kui-list-inset-right: 0px;
+  --_kui-list-inset-bottom: 0px;
+  --_kui-list-inset-left: 0px;
+  --_kui-list-clearance-start: 0px;
+  --_kui-list-clearance-end: 0px;
+  --_kui-list-ring-room: 0px;
+  --_kui-list-max-height: none;
+  --_kui-list-min-height: 0px;
   --_kui-list-divider-top: transparent;
   --_kui-list-divider-right: transparent;
   --_kui-list-divider-bottom: transparent;
@@ -8,12 +24,22 @@
 
   display: flex;
   min-width: 0;
-  min-height: 0;
+  min-height: var(--_kui-list-min-height);
+  max-height: var(--_kui-list-max-height);
   box-sizing: border-box;
+  padding: calc(
+      var(--_kui-list-inset-top, 0px) + var(--_kui-list-clearance-start)
+    )
+    var(--_kui-list-inset-right, 0)
+    calc(var(--_kui-list-inset-bottom, 0px) + var(--_kui-list-clearance-end))
+    var(--_kui-list-inset-left, 0);
   flex: var(--_kui-list-flex, initial);
   flex-direction: column;
   align-items: stretch;
-  gap: var(--_kui-list-gap, 0);
+  align-content: space-between;
+  justify-content: flex-start;
+  column-gap: var(--_kui-list-column-gap);
+  row-gap: var(--_kui-list-row-gap);
   box-shadow:
     inset 0 1px var(--_kui-list-divider-top),
     inset -1px 0 var(--_kui-list-divider-right),
@@ -21,23 +47,204 @@
     inset 1px 0 var(--_kui-list-divider-left);
 }
 
+.kui-list[data-control-insets*="t"] {
+  --_kui-list-inset-top: var(--kui-layout-inline-margin, 0.5rem);
+}
+
+.kui-list[data-control-insets*="r"] {
+  --_kui-list-inset-right: var(--kui-layout-inline-margin, 0.5rem);
+}
+
+.kui-list[data-control-insets*="b"] {
+  --_kui-list-inset-bottom: var(--kui-layout-inline-margin, 0.5rem);
+}
+
+.kui-list[data-control-insets*="l"] {
+  --_kui-list-inset-left: var(--kui-layout-inline-margin, 0.5rem);
+}
+
+.kui-list[data-text-insets*="t"] {
+  --_kui-list-inset-top: calc(
+    var(--kui-layout-inline-margin, 0.5rem) + 1px +
+      var(--kui-layout-item-padding, 0.5rem)
+  );
+}
+
+.kui-list[data-text-insets*="r"] {
+  --_kui-list-inset-right: calc(
+    var(--kui-layout-inline-margin, 0.5rem) + 1px +
+      var(--kui-layout-item-padding, 0.5rem)
+  );
+}
+
+.kui-list[data-text-insets*="b"] {
+  --_kui-list-inset-bottom: calc(
+    var(--kui-layout-inline-margin, 0.5rem) + 1px +
+      var(--kui-layout-item-padding, 0.5rem)
+  );
+}
+
+.kui-list[data-text-insets*="l"] {
+  --_kui-list-inset-left: calc(
+    var(--kui-layout-inline-margin, 0.5rem) + 1px +
+      var(--kui-layout-item-padding, 0.5rem)
+  );
+}
+
+/* `inset="document"`: a reading inset on all four sides that replaces any
+   side-selected text or control inset. */
+.kui-list[data-inset="document"] {
+  --_kui-list-inset-top: var(--kui-space-l);
+  --_kui-list-inset-right: var(--kui-space-xl);
+  --_kui-list-inset-bottom: var(--kui-space-l);
+  --_kui-list-inset-left: var(--kui-space-xl);
+}
+
+@media (max-width: 36rem) {
+  .kui-list[data-inset="document"] {
+    --_kui-list-inset-right: var(--kui-space-m);
+    --_kui-list-inset-left: var(--kui-space-m);
+  }
+}
+
+/* `frame`: a bordered, rounded stack (a result picker). Its 4px inset on
+   every side replaces any side-selected or document inset, and is exactly
+   the reach of a row's focus ring (3px ring, 1px offset), so the first and
+   last rows' rings stay inside a scrolling frame's clip at the scroll
+   extremes. (The ring-room scroll padding every scrollable List carries
+   handles a row stopped mid-scroll.) */
+.kui-list[data-frame="true"] {
+  --_kui-list-inset-top: var(--kui-space-2xs);
+  --_kui-list-inset-right: var(--kui-space-2xs);
+  --_kui-list-inset-bottom: var(--kui-space-2xs);
+  --_kui-list-inset-left: var(--kui-space-2xs);
+  border: 1px solid var(--kui-color-neutral-border-normal);
+  border-radius: var(--kui-radius-m);
+}
+
+.kui-list[data-h-align="left"] {
+  align-items: flex-start;
+  align-content: flex-start;
+}
+
+.kui-list[data-h-align="center"] {
+  align-items: center;
+  align-content: space-around;
+}
+
+.kui-list[data-h-align="right"] {
+  align-items: flex-end;
+  align-content: flex-end;
+}
+
+.kui-list[data-v-align="middle"] {
+  justify-content: space-around;
+}
+
+.kui-list[data-v-align="bottom"] {
+  justify-content: flex-end;
+}
+
+.kui-list[data-v-align="full"] {
+  justify-content: space-between;
+}
+
+/* A scrollable List's scroll padding is a row's focus-ring reach (3px ring,
+   1px offset) plus 2px of slack, so a row focused or scrolled into view stops
+   with its ring inside the clip rather than flush against it: Chromium's
+   focus scroll stops 1px short of the padded target, and a row's fractional
+   position can cost another 0.3px. Scroll padding moves nothing at rest; at
+   the scroll extremes an unframed List's first and last rows still meet the
+   clip, which is what `frame`'s 4px inset is for. */
 .kui-list[data-scrollable="true"] {
+  --_kui-list-ring-room: calc(var(--kui-space-2xs) + 2px);
   overflow-y: auto;
   overscroll-behavior-y: contain;
 }
 
-.kui-list[divider-sides*="t"] {
+/* `scrollClearance`: chrome lying over the List's block edge (a dialog's
+   floating footer) publishes how far it covers that edge through the
+   inherited `--kui-scroll-clearance-block-*` context. The List adds it to its
+   own block padding and scroll padding, so rows scroll visibly beneath the
+   chrome while the first and last rows, and anything focused or scrolled into
+   view, still come to rest clear of it. */
+.kui-list:is(
+  [data-scroll-clearance="block-start"],
+  [data-scroll-clearance="both"]
+) {
+  --_kui-list-clearance-start: var(--kui-scroll-clearance-block-start, 0px);
+}
+
+.kui-list:is(
+  [data-scroll-clearance="block-end"],
+  [data-scroll-clearance="both"]
+) {
+  --_kui-list-clearance-end: var(--kui-scroll-clearance-block-end, 0px);
+}
+
+.kui-list:is([data-scroll-clearance], [data-scrollable="true"]) {
+  scroll-padding-block: calc(
+      var(--_kui-list-clearance-start) + var(--_kui-list-ring-room)
+    )
+    calc(var(--_kui-list-clearance-end) + var(--_kui-list-ring-room));
+}
+
+/* In a Pane's scrolling content, a List that does not scroll itself keeps
+   its full height rather than shrinking to the content box. A shrunken List
+   lets its rows overflow its own box, and the scroller's block-end padding
+   (a bottom safe area, an overlay NavStack bottom toolbar's clearance)
+   follows the List's box, not those rows, so the last row could never
+   scroll clear of the edge. A `flex` basis still grows the List to fill. */
+.kui-pane > .kui-pane__content > .kui-list:not([data-scrollable="true"]) {
+  flex-shrink: 0;
+}
+
+/* A scrollable List owns the overflow, so its rows keep their natural height
+   and scroll rather than shrink. Items that clip their own overflow (a
+   ListItem) have a zero automatic minimum height, so the default
+   `flex-shrink: 1` compressed multiline rows into one another once the List
+   was bounded by a max-height ancestor. */
+.kui-list[data-scrollable="true"] > * {
+  flex-shrink: 0;
+}
+
+/* A scrollable List is a keyboard-focusable scroller: Chromium focuses it on
+   Tab when it holds no focusable rows, and a dialog may pick it as its first
+   focusable area. Its ring sits inside its box, so a rounded or clipping
+   parent cannot cut it off, and rounds with the standard control radius. */
+.kui-list[data-scrollable="true"]:focus-visible {
+  border-radius: var(--kui-radius-m);
+  outline: var(--kui-focus-ring);
+  outline-offset: -3px;
+}
+
+.kui-list:is([divider-sides*="t"], [data-scroll-divider*="t"]) {
   --_kui-list-divider-top: var(--kui-list-divider-color);
 }
 
-.kui-list[divider-sides*="r"] {
+.kui-list:is([divider-sides*="r"], [data-scroll-divider*="r"]) {
   --_kui-list-divider-right: var(--kui-list-divider-color);
 }
 
-.kui-list[divider-sides*="b"] {
+.kui-list:is([divider-sides*="b"], [data-scroll-divider*="b"]) {
   --_kui-list-divider-bottom: var(--kui-list-divider-color);
 }
 
-.kui-list[divider-sides*="l"] {
+.kui-list:is([divider-sides*="l"], [data-scroll-divider*="l"]) {
   --_kui-list-divider-left: var(--kui-list-divider-color);
 }
+
+/* `surface`: a solid background behind the stack and its insets. */
+.kui-list[data-surface="base"] {
+  background: var(--kui-color-surface);
+}
+
+.kui-list[data-surface="raised"] {
+  background: var(--kui-color-surface-raised);
+}
+
+/* `fill`: the layout root of a definite-height parent (an app root or a
+   fixed-height frame) takes its full height. Inside a flex layout use `flex`. */
+.kui-list[data-fill="true"] {
+  height: 100%;
+}

package/dist/styles/loading-spinner.css

@@ -5,6 +5,10 @@
   overflow: visible;
   fill: currentColor;
 }
+.kui-loading-spinner[data-size] {
+  width: var(--_kui-loading-spinner-size);
+  height: var(--_kui-loading-spinner-size);
+}
 .kui-loading-spinner path {
   transform-origin: 12px 12px;
   animation: kui-loading-spinner-rotate 0.85s linear infinite;

package/dist/styles/lucide-icon.css

@@ -4,3 +4,12 @@
   height: 1em;
   flex: none;
 }
+
+[data-lucide][data-inline="true"] {
+  display: inline-block;
+}
+
+[data-lucide][data-size] {
+  width: var(--_kui-lucide-size);
+  height: var(--_kui-lucide-size);
+}

package/dist/styles/nav-stack.css

@@ -1,4 +1,5 @@
 .kui-nav-stack {
+  position: relative;
   display: flex;
   min-width: 0;
   min-height: 0;
@@ -6,87 +7,155 @@
   overflow: hidden;
   flex-direction: column;
   background: var(--kui-color-surface);
+  /* Safe areas: the stack's surfaces paint through unsafe areas; its chrome,
+     bottom toolbar, and each view compensate for the edges the stack still
+     touches (see pane.css for the `--kui-edge-inset-*` edge context). */
+  --_kui-nav-stack-safe-block-start: var(
+    --kui-edge-inset-block-start,
+    var(--kui-safe-area-block-start, env(safe-area-inset-top, 0px))
+  );
+  --_kui-nav-stack-safe-block-end: var(
+    --kui-edge-inset-block-end,
+    var(--kui-safe-area-block-end, env(safe-area-inset-bottom, 0px))
+  );
+  --_kui-nav-stack-safe-inline-start: var(
+    --kui-edge-inset-inline-start,
+    var(--kui-safe-area-inline-start, env(safe-area-inset-left, 0px))
+  );
+  --_kui-nav-stack-safe-inline-end: var(
+    --kui-edge-inset-inline-end,
+    var(--kui-safe-area-inline-end, env(safe-area-inset-right, 0px))
+  );
 }
 
-.kui-nav-stack__chrome {
-  display: flex;
-  min-width: 0;
-  min-height: calc(2px + 2.625rem);
-  padding-inline: var(--kui-space-xs);
-  align-items: center;
-  gap: var(--kui-space-xs);
-  background: var(--kui-color-surface);
-}
-
-.kui-nav-stack__lead {
-  display: flex;
-  flex: 1;
-  min-width: 0;
-  align-items: center;
-  gap: var(--kui-space-2xs);
-}
-
-.kui-nav-stack__back {
-  display: grid;
-  width: 2.5rem;
-  height: 2.5rem;
-  padding: 0;
-  border: 1px solid transparent;
-  border-radius: var(--kui-layout-rounded-radius, calc(1px + 0.6875rem));
-  color: inherit;
-  background: transparent;
-  cursor: pointer;
-  place-items: center;
+.kui-nav-stack__chrome,
+.kui-nav-stack__bottom {
+  --kui-edge-inset-block-start: 0px;
+  --kui-edge-inset-block-end: 0px;
+  --kui-edge-inset-inline-start: 0px;
+  --kui-edge-inset-inline-end: 0px;
+  transition: opacity var(--kui-nav-stack-transition-duration, 200ms) ease;
 }
 
-.kui-nav-stack__back:hover {
-  border-color: var(--kui-color-border);
-  background: var(--kui-color-neutral-fill-normal);
+/* Establish the starting opacity instantly; only the release animates. */
+.kui-nav-stack__chrome--entering {
+  transition: none;
+  opacity: 0;
 }
 
-.kui-nav-stack__back:focus-visible {
-  outline: var(--kui-focus-ring);
-  outline-offset: 1px;
+.kui-nav-stack__chrome-copy {
+  position: absolute;
+  z-index: 2;
+  inset-block-start: 0;
+  inset-inline: 0;
+  pointer-events: none;
+  transition: opacity var(--kui-nav-stack-transition-duration, 200ms) ease;
 }
 
-.kui-nav-stack__back-icon {
-  display: block;
+.kui-nav-stack__chrome-copy--bottom {
+  inset-block: auto 0;
 }
 
-/* The title is ToolbarText (which owns its font, height, and ellipsis); it just
-   needs to flex to fill the lead zone beside the back control. */
-.kui-nav-stack__title {
-  flex: 1 1 auto;
-  min-width: 0;
+.kui-nav-stack__chrome-copy--exiting {
+  opacity: 0;
 }
 
-.kui-nav-stack__actions {
-  display: flex;
-  align-items: center;
-  gap: var(--kui-space-2xs);
+/* The chrome hosts the stack's real top Toolbar. It hands that toolbar the
+   edges the stack still touches through the edge context (never the bottom,
+   which the viewport owns); the toolbar pads for the sides it claims with
+   `safeAreaEdges` while its box paints through them. */
+.kui-nav-stack__chrome {
+  --kui-edge-inset-block-start: var(--_kui-nav-stack-safe-block-start);
+  --kui-edge-inset-inline-start: var(--_kui-nav-stack-safe-inline-start);
+  --kui-edge-inset-inline-end: var(--_kui-nav-stack-safe-inline-end);
+  background: var(--kui-color-surface);
 }
 
 .kui-nav-stack__viewport {
+  --kui-edge-inset-block-start: var(--_kui-nav-stack-safe-block-start);
+  --kui-edge-inset-block-end: var(--_kui-nav-stack-safe-block-end);
+  --kui-edge-inset-inline-start: var(--_kui-nav-stack-safe-inline-start);
+  --kui-edge-inset-inline-end: var(--_kui-nav-stack-safe-inline-end);
   position: relative;
   flex: 1;
   min-height: 0;
   overflow: hidden;
 }
 
+/* The top chrome and the bottom toolbar own their edges; transient chrome
+   copies from a transition do not. */
+.kui-nav-stack__chrome ~ .kui-nav-stack__viewport {
+  --kui-edge-inset-block-start: 0px;
+}
+
+.kui-nav-stack__viewport:has(
+  ~ .kui-nav-stack__bottom:not(.kui-nav-stack__chrome-copy)
+) {
+  --kui-edge-inset-block-end: 0px;
+}
+
 .kui-nav-stack__view {
   position: absolute;
   overflow: auto;
   background: var(--kui-color-surface);
-  transition: transform 200ms ease;
+  transition: transform var(--kui-nav-stack-transition-duration, 200ms) ease;
   inset: 0;
 }
 
+.kui-nav-stack__view:has(> [data-component="pane"]) {
+  display: grid;
+  overflow: hidden;
+}
+
+/* Each view is its region's scroll owner: block insets become padding inside
+   the scroller so content scrolls under an unsafe edge but can always be
+   scrolled clear. A view whose only child is a Pane or layout lets that child
+   own the insets instead. */
+.kui-nav-stack__view:not(
+  :has(
+    > :is(
+        [data-component="pane"],
+        [data-component="nav-stack"],
+        [data-component="split-view"],
+        [data-component="workbench"],
+        [data-component="tab-scaffold"]
+      ):only-child
+  )
+) {
+  padding-block: var(--kui-edge-inset-block-start)
+    var(--kui-edge-inset-block-end);
+  padding-inline: var(--kui-edge-inset-inline-start)
+    var(--kui-edge-inset-inline-end);
+  scroll-padding-block: var(--kui-edge-inset-block-start)
+    var(--kui-edge-inset-block-end);
+}
+
+.kui-nav-stack__view
+  > :not(
+    :is(
+      [data-component="pane"],
+      [data-component="nav-stack"],
+      [data-component="split-view"],
+      [data-component="workbench"],
+      [data-component="tab-scaffold"]
+    ):only-child
+  ) {
+  --kui-edge-inset-block-start: 0px;
+  --kui-edge-inset-block-end: 0px;
+  --kui-edge-inset-inline-start: 0px;
+  --kui-edge-inset-inline-end: 0px;
+}
+
 /* Only the active view (and any view mid-exit) is shown; lower entries stay
    mounted for state/focus but hidden behind it. */
 .kui-nav-stack__view[data-nav-active="false"] {
   visibility: hidden;
 }
 
+.kui-nav-stack__view[data-nav-revealed="true"] {
+  visibility: visible;
+}
+
 .kui-nav-stack__view[data-nav-exiting="true"] {
   z-index: 1;
   visibility: visible;
@@ -94,18 +163,180 @@
 
 /* Push: the incoming view starts off the trailing edge and slides to rest.
    Pop: the outgoing view starts at rest and slides off the trailing edge. */
+/* Establish the offscreen start without first transitioning toward it. */
+.kui-nav-stack__view--entering {
+  transition: none;
+}
+
 .kui-nav-stack__view--entering,
 .kui-nav-stack__view--exiting {
   transform: translateX(100%);
 }
 
 .kui-nav-stack__bottom {
-  border-block-start: 1px solid var(--kui-color-border);
+  --kui-edge-inset-block-end: var(--_kui-nav-stack-safe-block-end);
+  --kui-edge-inset-inline-start: var(--_kui-nav-stack-safe-inline-start);
+  --kui-edge-inset-inline-end: var(--_kui-nav-stack-safe-inline-end);
+  border-block-start: 1px solid
+    var(--_kui-nav-stack-bottom-divider, transparent);
   background: var(--kui-color-surface);
 }
 
+/* The live chrome is the containing block of its scroll divider; a
+   cross-fading copy stays absolutely positioned. */
+.kui-nav-stack__chrome:not(.kui-nav-stack__chrome-copy) {
+  position: relative;
+}
+
+/* `chromePresentation="overlay"`: the top chrome (and any copy cross-fading
+   out of it) paints the translucent chrome material (opaque under reduced
+   transparency or increased contrast, without `backdrop-filter`, or in
+   forced colors). Once `wireNavStack` has measured the live chrome
+   (`data-chrome-overlay="measured"`, with its border-box block size, top
+   safe area included, published on this root), the chrome lies over the
+   viewport's top edge and the viewport hands that size to its views as the
+   block-start edge context, so a plain view, a sole Pane, or a nested layout
+   pads and scroll-pads by it: content scrolls beneath the chrome yet rests
+   clear of it. Unwired, the chrome stays docked in its own band, so it never
+   covers content it has not measured. */
+.kui-nav-stack[data-chrome-presentation="overlay"] > .kui-nav-stack__chrome {
+  -webkit-backdrop-filter: var(--kui-chrome-material-filter);
+  backdrop-filter: var(--kui-chrome-material-filter);
+  background: var(--kui-chrome-material);
+}
+
+.kui-nav-stack[data-chrome-presentation="overlay"][data-chrome-overlay="measured"]
+  > .kui-nav-stack__chrome:not(.kui-nav-stack__chrome-copy) {
+  position: absolute;
+  z-index: 2;
+  inset-block-start: 0;
+  /* A classic (space-taking) vertical scrollbar in the active view stays
+     uncovered: `wireNavStack` publishes its inline size, so the chrome ends
+     where the track begins and its thumb and arrows stay usable. An overlay
+     scrollbar takes no space and passes beneath the material like the
+     content. */
+  inset-inline: 0 var(--_kui-nav-stack-scrollbar-inline-size, 0px);
+}
+
+.kui-nav-stack[data-chrome-presentation="overlay"][data-chrome-overlay="measured"]
+  > .kui-nav-stack__viewport {
+  --kui-edge-inset-block-start: var(--_kui-nav-stack-chrome-block-size, 0px);
+}
+
+/* `bottomToolbarPresentation="overlay"`: the bottom toolbar (and any copy
+   cross-fading out of it) paints the same material. Once `wireNavStack` has
+   measured the live toolbar (`data-bottom-toolbar-overlay="measured"`, with
+   its border-box block size, bottom safe area and scroll-divider border
+   included, published on this root), the toolbar lies over the viewport's
+   bottom edge and the viewport hands that size to its views as the
+   block-end edge context (outranking the docked rule above that zeroes it),
+   so a plain view, a sole Pane's content or footer, or a nested layout pads
+   and scroll-pads by it: content scrolls beneath the toolbar yet its last
+   item rests clear of it. Unwired, the toolbar stays docked. */
+.kui-nav-stack[data-bottom-toolbar-presentation="overlay"]
+  > .kui-nav-stack__bottom {
+  -webkit-backdrop-filter: var(--kui-chrome-material-filter);
+  backdrop-filter: var(--kui-chrome-material-filter);
+  background: var(--kui-chrome-material);
+}
+
+.kui-nav-stack[data-bottom-toolbar-presentation="overlay"][data-bottom-toolbar-overlay="measured"]
+  > .kui-nav-stack__bottom:not(.kui-nav-stack__chrome-copy) {
+  position: absolute;
+  z-index: 2;
+  inset-block-end: 0;
+  /* Like the top chrome, it ends where a classic scrollbar's track begins. */
+  inset-inline: 0 var(--_kui-nav-stack-bottom-scrollbar-inline-size, 0px);
+}
+
+.kui-nav-stack[data-bottom-toolbar-presentation="overlay"][data-bottom-toolbar-overlay="measured"]
+  > .kui-nav-stack__viewport {
+  --kui-edge-inset-block-end: var(--_kui-nav-stack-bottom-block-size, 0px);
+}
+
+@media (forced-colors: active) {
+  .kui-nav-stack[data-chrome-presentation="overlay"] > .kui-nav-stack__chrome {
+    -webkit-backdrop-filter: none;
+    backdrop-filter: none;
+    background: Canvas;
+    border-block-end: 1px solid CanvasText;
+  }
+
+  /* Its always-present 1px top border becomes the visible edge. */
+  .kui-nav-stack[data-bottom-toolbar-presentation="overlay"]
+    > .kui-nav-stack__bottom {
+    -webkit-backdrop-filter: none;
+    backdrop-filter: none;
+    background: Canvas;
+    border-block-start-color: CanvasText;
+  }
+}
+
+/* Chrome dividers: with `chromeDividers="scroll"` (the default, no
+   attribute) the top chrome draws a line along its bottom edge while the
+   active view's content is scrolled beneath it, and the bottom toolbar
+   colors its 1px top border while more content lies below it — never when
+   the content fits. `wireScrollDividers` reports that state through
+   `data-scroll-divider`; `always` draws both lines without it, and `none`
+   neither, whatever it reports. The chrome's line is an overlaid 1px pseudo-element
+   (whatever the chrome holds never covers it) and the bottom's border is
+   always there, so showing either never moves the chrome, the toolbar, or
+   the content. A cross-fading chrome copy keeps the line its snapshot had.
+   With `separator="auto"`, an active sunken Pane also colors both available
+   edges; `hidden` suppresses the stack-owned lines. */
+.kui-nav-stack[data-separator="auto"]:has(
+    > .kui-nav-stack__viewport
+      > .kui-nav-stack__view[data-nav-active="true"]
+      > [data-component="pane"][data-appearance="sunken"]
+  )
+  > .kui-nav-stack__chrome::after,
+.kui-nav-stack[data-separator="auto"]:not([data-chrome-dividers])
+  > .kui-nav-stack__chrome[data-scroll-divider*="b"]::after,
+.kui-nav-stack[data-separator="auto"][data-chrome-dividers="always"]
+  > .kui-nav-stack__chrome::after {
+  position: absolute;
+  block-size: 1px;
+  background: var(--kui-color-neutral-border-normal);
+  content: "";
+  inset-block-end: 0;
+  inset-inline: 0;
+  pointer-events: none;
+}
+
+.kui-nav-stack[data-separator="auto"]:has(
+    > .kui-nav-stack__viewport
+      > .kui-nav-stack__view[data-nav-active="true"]
+      > [data-component="pane"][data-appearance="sunken"]
+  )
+  > .kui-nav-stack__bottom,
+.kui-nav-stack[data-separator="auto"]:not([data-chrome-dividers])
+  > .kui-nav-stack__bottom[data-scroll-divider*="t"],
+.kui-nav-stack[data-separator="auto"][data-chrome-dividers="always"]
+  > .kui-nav-stack__bottom {
+  --_kui-nav-stack-bottom-divider: var(--kui-color-neutral-border-normal);
+}
+
 @media (prefers-reduced-motion: reduce) {
-  .kui-nav-stack__view {
+  .kui-nav-stack__view,
+  .kui-nav-stack__chrome,
+  .kui-nav-stack__bottom,
+  .kui-nav-stack__chrome-copy {
     transition: none;
   }
 }
+
+/* As the only child of a Workbench region (its main area or a panel's
+   content, which the Workbench marks with `data-workbench-main` /
+   `data-workbench-panel-content`), a NavStack fills the region, so a
+   composed toolbar's footer (or the app's own) sits at the region's bottom
+   edge rather than under short content. */
+:is([data-workbench-main], [data-workbench-panel-content])
+  > [data-component="nav-stack"]:only-child {
+  height: 100%;
+  --kui-edge-inset-block-start: var(--_kui-workbench-content-edge-block-start);
+  --kui-edge-inset-block-end: var(--_kui-workbench-content-edge-block-end);
+  --kui-edge-inset-inline-start: var(
+    --_kui-workbench-content-edge-inline-start
+  );
+  --kui-edge-inset-inline-end: var(--_kui-workbench-content-edge-inline-end);
+}