@kerfjs/ui 5.0.0-beta.11 → 5.0.0-beta.111

package/dist/styles/components/media/lucide-icon/lucide-icon.css

@@ -0,0 +1,15 @@
+[data-lucide] {
+  display: block;
+  width: 1em;
+  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/components/navigation/disclosure-arrow/disclosure-arrow.css

@@ -0,0 +1,43 @@
+.kui-disclosure-arrow {
+  display: inline-flex;
+  width: var(--kui-disclosure-arrow-size, 1.125rem);
+  height: var(--kui-disclosure-arrow-size, 1.125rem);
+  flex: none;
+  align-items: center;
+  justify-content: center;
+  transform: rotate(var(--_kui-disclosure-arrow-rotation, 0deg));
+  transform-origin: center;
+  transition: transform var(--kui-disclosure-arrow-duration, 0.2s) ease;
+}
+
+.kui-disclosure-arrow svg {
+  display: block;
+  width: 100%;
+  height: 100%;
+}
+
+/* In a Disclosure the native <details> owns the open state, so the arrow
+   follows its live [open] rather than the render-time rotation. */
+.kui-disclosure > .kui-disclosure__summary > .kui-disclosure-arrow {
+  transform: rotate(0deg);
+}
+
+.kui-disclosure[open] > .kui-disclosure__summary > .kui-disclosure-arrow {
+  transform: rotate(90deg);
+}
+
+.kui-disclosure:dir(rtl) > .kui-disclosure__summary > .kui-disclosure-arrow {
+  transform: rotate(180deg);
+}
+
+.kui-disclosure[open]:dir(rtl)
+  > .kui-disclosure__summary
+  > .kui-disclosure-arrow {
+  transform: rotate(90deg);
+}
+
+@media (prefers-reduced-motion: reduce) {
+  .kui-disclosure-arrow {
+    transition-duration: 0s;
+  }
+}

package/dist/styles/components/navigation/nav-stack/nav-stack.css

@@ -0,0 +1,619 @@
+.kui-nav-stack {
+  position: relative;
+  display: flex;
+  min-width: 0;
+  min-height: 0;
+  height: 100%;
+  overflow: hidden;
+  flex-direction: column;
+  background: var(--_kui-nav-stack-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,
+.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;
+}
+
+/* Establish the starting opacity instantly; only the release animates. */
+.kui-nav-stack__chrome--entering {
+  transition: none;
+  opacity: 0;
+}
+
+.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__chrome-copy--bottom {
+  inset-block: auto 0;
+}
+
+.kui-nav-stack__chrome-copy--exiting {
+  opacity: 0;
+}
+
+/* `background`: the stack's color paints the stack, its docked chrome and
+   bottom toolbar, and every view (a view's own `pane.background` paints over
+   it). Overlay chrome keeps the chrome material. A nested stack never
+   inherits the color. Forced colors paint the system surface. */
+.kui-nav-stack:not([data-background]) {
+  --_kui-nav-stack-background: initial;
+}
+
+@media (forced-colors: active) {
+  .kui-nav-stack[data-background],
+  .kui-nav-stack[data-background]
+    > :is(.kui-nav-stack__chrome, .kui-nav-stack__bottom),
+  .kui-nav-stack[data-background]
+    > .kui-nav-stack__viewport
+    > .kui-nav-stack__view {
+    background: Canvas;
+  }
+}
+
+/* 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-nav-stack-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-nav-stack-background, var(--kui-color-surface));
+  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;
+}
+
+/* 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 {
+  --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-nav-stack-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);
+}
+
+/* The material's surface context at rest (see pane.css); clear chrome keeps
+   the inherited context. */
+.kui-nav-stack[data-chrome-presentation="overlay"]:not(
+    [data-chrome-material="clear"]
+  )
+  > .kui-nav-stack__chrome,
+.kui-nav-stack[data-bottom-toolbar-presentation="overlay"]:not(
+    [data-bottom-toolbar-material="clear"]
+  )
+  > .kui-nav-stack__bottom {
+  --kui-color-surface-current-tint: 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;
+  }
+}
+
+/* An overlay bar cross-fades its contents, never its material. Fading the
+   bar itself would fade its backdrop filter with it (WebKit drops the blur
+   outright), so mid push or pop the sliding views would show through the
+   chrome. Instead the live bar keeps its material at full opacity while its
+   contents fade in, and the copy cross-fading out above it carries no
+   material of its own (nor a clear bar's scroll edge), only the old
+   contents and divider. */
+.kui-nav-stack[data-chrome-presentation="overlay"] > .kui-nav-stack__chrome,
+.kui-nav-stack[data-bottom-toolbar-presentation="overlay"]
+  > .kui-nav-stack__bottom {
+  opacity: 1;
+  transition: none;
+}
+
+.kui-nav-stack[data-chrome-presentation="overlay"]
+  > .kui-nav-stack__chrome:not(.kui-nav-stack__chrome-copy)
+  > *,
+.kui-nav-stack[data-bottom-toolbar-presentation="overlay"]
+  > .kui-nav-stack__bottom:not(.kui-nav-stack__chrome-copy)
+  > * {
+  transition: opacity var(--kui-nav-stack-transition-duration, 200ms) ease;
+}
+
+.kui-nav-stack[data-chrome-presentation="overlay"]
+  > .kui-nav-stack__chrome--entering:not(.kui-nav-stack__chrome-copy)
+  > *,
+.kui-nav-stack[data-bottom-toolbar-presentation="overlay"]
+  > .kui-nav-stack__chrome--entering:not(.kui-nav-stack__chrome-copy)
+  > * {
+  transition: none;
+  opacity: 0;
+}
+
+.kui-nav-stack[data-chrome-presentation="overlay"]
+  > .kui-nav-stack__chrome.kui-nav-stack__chrome-copy,
+.kui-nav-stack[data-bottom-toolbar-presentation="overlay"]
+  > .kui-nav-stack__bottom.kui-nav-stack__chrome-copy {
+  -webkit-backdrop-filter: none;
+  backdrop-filter: none;
+  background: transparent;
+  transition: opacity var(--kui-nav-stack-transition-duration, 200ms) ease;
+}
+
+.kui-nav-stack[data-chrome-presentation="overlay"]
+  > .kui-nav-stack__chrome.kui-nav-stack__chrome-copy--exiting,
+.kui-nav-stack[data-bottom-toolbar-presentation="overlay"]
+  > .kui-nav-stack__bottom.kui-nav-stack__chrome-copy--exiting {
+  opacity: 0;
+}
+
+.kui-nav-stack[data-chrome-material="clear"][data-scroll-edge]
+  > .kui-nav-stack__chrome.kui-nav-stack__chrome-copy::before,
+.kui-nav-stack[data-bottom-toolbar-material="clear"][data-scroll-edge]
+  > .kui-nav-stack__bottom.kui-nav-stack__chrome-copy::before {
+  content: none;
+}
+
+/* `clear` chrome and bottom toolbar: overlay bars (the same measuring,
+   placement, and edge insets as above) that are fully transparent, for
+   chrome over imagery. With `scrollEdge="material"` a pseudo-element
+   carrying the chrome material fades in (opacity only) while the active
+   view's content lies beneath the bar, as `wireScrollDividers` reports, and
+   out at rest. Clear bars draw no scroll divider. */
+.kui-nav-stack[data-chrome-material="clear"] > .kui-nav-stack__chrome {
+  -webkit-backdrop-filter: none;
+  backdrop-filter: none;
+  background: transparent;
+}
+
+:where(.kui-nav-stack[data-chrome-material="clear"][data-scroll-edge])
+  > .kui-nav-stack__chrome:not(.kui-nav-stack__chrome-copy) {
+  position: relative;
+  isolation: isolate;
+}
+
+/* The scroll edge fades in as content scrolls beneath the bar: the wiring
+   publishes `--kui-scroll-edge-progress` (0 at rest, 1 once content lies
+   `scrollEdgeDistance` beyond the bar) and only the layer's opacity follows
+   it; the filter never animates. Unwired, it stays clear. */
+.kui-nav-stack[data-chrome-material="clear"][data-scroll-edge]
+  > .kui-nav-stack__chrome::before {
+  position: absolute;
+  z-index: -1;
+  content: "";
+  inset: 0;
+  opacity: var(--kui-scroll-edge-progress, 0);
+  pointer-events: none;
+}
+
+.kui-nav-stack[data-chrome-material="clear"][data-scroll-edge="material"]
+  > .kui-nav-stack__chrome::before {
+  -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-material="clear"][data-scroll-edge="surface"]
+  > .kui-nav-stack__chrome::before {
+  background: var(--kui-color-surface);
+}
+
+/* Static effects and slow displays snap the edge on while content lies
+   beneath the bar instead of tracking the scroll. */
+:root[data-kui-effects="static"]
+  .kui-nav-stack[data-chrome-material="clear"][data-scroll-edge]
+  > .kui-nav-stack__chrome::before {
+  opacity: 0;
+}
+
+:root[data-kui-effects="static"]
+  .kui-nav-stack[data-chrome-material="clear"][data-scroll-edge]
+  > .kui-nav-stack__chrome[data-scroll-divider*="b"]::before {
+  opacity: 1;
+}
+
+@media (update: slow) {
+  .kui-nav-stack[data-chrome-material="clear"][data-scroll-edge]
+    > .kui-nav-stack__chrome::before {
+    opacity: 0;
+  }
+
+  .kui-nav-stack[data-chrome-material="clear"][data-scroll-edge]
+    > .kui-nav-stack__chrome[data-scroll-divider*="b"]::before {
+    opacity: 1;
+  }
+}
+
+/* Clear chrome turns opaque where transparency would hurt, like the
+   material itself. */
+@media (prefers-reduced-transparency: reduce), (prefers-contrast: more) {
+  .kui-nav-stack[data-chrome-material="clear"] > .kui-nav-stack__chrome {
+    background: var(--kui-chrome-material);
+  }
+}
+
+@media (forced-colors: active) {
+  .kui-nav-stack[data-chrome-material="clear"] > .kui-nav-stack__chrome {
+    background: Canvas;
+    border-block-end: 1px solid CanvasText;
+  }
+
+  .kui-nav-stack[data-chrome-material="clear"][data-scroll-edge]
+    > .kui-nav-stack__chrome::before {
+    content: none;
+  }
+}
+
+.kui-nav-stack[data-bottom-toolbar-material="clear"] > .kui-nav-stack__bottom {
+  -webkit-backdrop-filter: none;
+  backdrop-filter: none;
+  background: transparent;
+}
+
+:where(.kui-nav-stack[data-bottom-toolbar-material="clear"][data-scroll-edge])
+  > .kui-nav-stack__bottom:not(.kui-nav-stack__chrome-copy) {
+  position: relative;
+  isolation: isolate;
+}
+
+/* The scroll edge fades in as content scrolls beneath the bar: the wiring
+   publishes `--kui-scroll-edge-progress` (0 at rest, 1 once content lies
+   `scrollEdgeDistance` beyond the bar) and only the layer's opacity follows
+   it; the filter never animates. Unwired, it stays clear. */
+.kui-nav-stack[data-bottom-toolbar-material="clear"][data-scroll-edge]
+  > .kui-nav-stack__bottom::before {
+  position: absolute;
+  z-index: -1;
+  content: "";
+  inset: 0;
+  opacity: var(--kui-scroll-edge-progress, 0);
+  pointer-events: none;
+}
+
+.kui-nav-stack[data-bottom-toolbar-material="clear"][data-scroll-edge="material"]
+  > .kui-nav-stack__bottom::before {
+  -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-material="clear"][data-scroll-edge="surface"]
+  > .kui-nav-stack__bottom::before {
+  background: var(--kui-color-surface);
+}
+
+/* Static effects and slow displays snap the edge on while content lies
+   beneath the bar instead of tracking the scroll. */
+:root[data-kui-effects="static"]
+  .kui-nav-stack[data-bottom-toolbar-material="clear"][data-scroll-edge]
+  > .kui-nav-stack__bottom::before {
+  opacity: 0;
+}
+
+:root[data-kui-effects="static"]
+  .kui-nav-stack[data-bottom-toolbar-material="clear"][data-scroll-edge]
+  > .kui-nav-stack__bottom[data-scroll-divider*="t"]::before {
+  opacity: 1;
+}
+
+@media (update: slow) {
+  .kui-nav-stack[data-bottom-toolbar-material="clear"][data-scroll-edge]
+    > .kui-nav-stack__bottom::before {
+    opacity: 0;
+  }
+
+  .kui-nav-stack[data-bottom-toolbar-material="clear"][data-scroll-edge]
+    > .kui-nav-stack__bottom[data-scroll-divider*="t"]::before {
+    opacity: 1;
+  }
+}
+
+/* Clear chrome turns opaque where transparency would hurt, like the
+   material itself. */
+@media (prefers-reduced-transparency: reduce), (prefers-contrast: more) {
+  .kui-nav-stack[data-bottom-toolbar-material="clear"]
+    > .kui-nav-stack__bottom {
+    background: var(--kui-chrome-material);
+  }
+}
+
+@media (forced-colors: active) {
+  .kui-nav-stack[data-bottom-toolbar-material="clear"]
+    > .kui-nav-stack__bottom {
+    background: Canvas;
+    border-block-start-color: CanvasText;
+  }
+
+  .kui-nav-stack[data-bottom-toolbar-material="clear"][data-scroll-edge]
+    > .kui-nav-stack__bottom::before {
+    content: none;
+  }
+}
+
+/* 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],
+    [data-chrome-material="clear"]
+  )
+  > .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],
+    [data-bottom-toolbar-material="clear"]
+  )
+  > .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__chrome,
+  .kui-nav-stack__bottom,
+  .kui-nav-stack__chrome-copy,
+  .kui-nav-stack[data-chrome-presentation="overlay"]
+    > .kui-nav-stack__chrome
+    > *,
+  .kui-nav-stack[data-bottom-toolbar-presentation="overlay"]
+    > .kui-nav-stack__bottom
+    > * {
+    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);
+}