@kerfjs/ui 5.0.0-beta.74 → 5.0.0-beta.76

package/dist/styles/components/layout/pane/pane.css

@@ -0,0 +1,263 @@
+.kui-pane {
+  --kui-pane-separator-block-start-width: 0;
+  --kui-pane-separator-block-end-width: 0;
+  --kui-pane-separator-inline-start-width: 0;
+  --kui-pane-separator-inline-end-width: 0;
+
+  display: grid;
+  min-width: 0;
+  min-height: 0;
+  padding: 0;
+  box-sizing: border-box;
+  border: 0 solid
+    var(--kui-pane-separator-color, var(--kui-color-neutral-border-normal));
+  border-block-start-width: var(--kui-pane-separator-block-start-width);
+  border-block-end-width: var(--kui-pane-separator-block-end-width);
+  border-inline-start-width: var(--kui-pane-separator-inline-start-width);
+  border-inline-end-width: var(--kui-pane-separator-inline-end-width);
+  grid-template-areas:
+    "header"
+    "content"
+    "footer";
+  grid-template-rows: auto minmax(0, 1fr) auto;
+}
+
+/* Paint the active scroll owner once, so alpha lowered colors do not stack.
+   Fixed chrome leaves the content slot scrolling; auto chrome lets the Pane
+   root scroll in its short mode, while its content remains transparent. */
+.kui-pane[data-appearance="sunken"] > .kui-pane__content {
+  background: var(
+    --kui-sunken-panel-background,
+    var(--kui-color-surface-lowered)
+  );
+}
+
+.kui-pane[data-appearance="sunken"][data-chrome-placement="auto"] {
+  background: var(
+    --kui-sunken-panel-background,
+    var(--kui-color-surface-lowered)
+  );
+}
+
+.kui-pane[data-appearance="sunken"][data-chrome-placement="auto"]
+  > .kui-pane__content {
+  background: transparent;
+}
+
+.kui-pane[data-appearance="sunken"][data-chrome-placement="auto"]
+  > :is(.kui-pane__header, .kui-pane__footer) {
+  background: var(--kui-pane-chrome-background, var(--kui-color-surface));
+}
+
+/* Safe areas. The pane root never pads, so its background and separators paint
+   through an unsafe area; its slots compensate on the edges the pane still
+   touches. The inherited `--kui-edge-inset-*` context says how far each edge
+   still reaches into an unsafe area: layouts clear an edge a region does not
+   reach, and an unset edge means the full device inset. Every slot clears the
+   context once it has applied it, so nested content never double-insets. */
+.kui-pane {
+  --_kui-pane-safe-block-start: var(
+    --kui-edge-inset-block-start,
+    var(--kui-safe-area-block-start, env(safe-area-inset-top, 0px))
+  );
+  --_kui-pane-safe-block-end: var(
+    --kui-edge-inset-block-end,
+    var(--kui-safe-area-block-end, env(safe-area-inset-bottom, 0px))
+  );
+  --_kui-pane-safe-inline-start: var(
+    --kui-edge-inset-inline-start,
+    var(--kui-safe-area-inline-start, env(safe-area-inset-left, 0px))
+  );
+  --_kui-pane-safe-inline-end: var(
+    --kui-edge-inset-inline-end,
+    var(--kui-safe-area-inline-end, env(safe-area-inset-right, 0px))
+  );
+}
+
+.kui-pane[data-safe-area-block-start="false"] {
+  --_kui-pane-safe-block-start: 0px;
+}
+
+.kui-pane[data-safe-area-block-end="false"] {
+  --_kui-pane-safe-block-end: 0px;
+}
+
+.kui-pane[data-safe-area-inline-start="false"] {
+  --_kui-pane-safe-inline-start: 0px;
+}
+
+.kui-pane[data-safe-area-inline-end="false"] {
+  --_kui-pane-safe-inline-end: 0px;
+}
+
+.kui-pane[data-separator-block-start="true"] {
+  --kui-pane-separator-block-start-width: var(--kui-pane-separator-width, 1px);
+}
+
+.kui-pane[data-separator-block-end="true"] {
+  --kui-pane-separator-block-end-width: var(--kui-pane-separator-width, 1px);
+}
+
+.kui-pane[data-separator-inline-start="true"] {
+  --kui-pane-separator-inline-start-width: var(--kui-pane-separator-width, 1px);
+}
+
+.kui-pane[data-separator-inline-end="true"] {
+  --kui-pane-separator-inline-end-width: var(--kui-pane-separator-width, 1px);
+}
+
+/* Child selectors outrank the `.kui-content` reset the content slot also carries. */
+.kui-pane > :is(.kui-pane__header, .kui-pane__content, .kui-pane__footer) {
+  --kui-edge-inset-block-start: 0px;
+  --kui-edge-inset-block-end: 0px;
+  --kui-edge-inset-inline-start: 0px;
+  --kui-edge-inset-inline-end: 0px;
+  padding-inline: var(--_kui-pane-safe-inline-start)
+    var(--_kui-pane-safe-inline-end);
+}
+
+.kui-pane__header,
+.kui-pane__toolbar {
+  display: flex;
+  min-width: 0;
+  padding-block-start: var(--_kui-pane-safe-block-start);
+  flex-direction: column;
+  grid-area: header;
+}
+
+/* A header or footer holding only a Toolbar hands the toolbar its inline edges
+   instead of padding around it, so the toolbar's dividers still reach the
+   pane edge while its controls clear the unsafe area. */
+.kui-pane
+  > :is(.kui-pane__header, .kui-pane__footer):has(
+    > [data-component="toolbar"]:only-child
+  ) {
+  --kui-edge-inset-inline-start: var(--_kui-pane-safe-inline-start);
+  --kui-edge-inset-inline-end: var(--_kui-pane-safe-inline-end);
+  padding-inline: 0;
+}
+
+/* The scrolling content takes the block insets as padding inside the scroller
+   (and matching scroll padding), so content scrolls under an unsafe edge yet
+   its first and last items can always be scrolled clear of it. A header or
+   footer already owns that edge. */
+.kui-pane__content {
+  --_kui-pane-content-block-start: var(--_kui-pane-safe-block-start);
+  --_kui-pane-content-block-end: var(--_kui-pane-safe-block-end);
+  min-width: 0;
+  min-height: 0;
+  overflow: auto;
+  grid-area: content;
+  overscroll-behavior: contain;
+  scroll-padding-block: var(--_kui-pane-content-block-start)
+    var(--_kui-pane-content-block-end);
+}
+
+.kui-pane > .kui-pane__content {
+  padding-block: var(--_kui-pane-content-block-start)
+    var(--_kui-pane-content-block-end);
+}
+
+.kui-pane__header ~ .kui-pane__content {
+  --_kui-pane-content-block-start: 0px;
+}
+
+.kui-pane__content:has(~ .kui-pane__footer) {
+  --_kui-pane-content-block-end: 0px;
+}
+
+.kui-pane__footer {
+  display: flex;
+  min-width: 0;
+  padding-block-end: var(--_kui-pane-safe-block-end);
+  flex-direction: column;
+  grid-area: footer;
+}
+
+/* Chrome dividers: one line under the header and one over the footer, where
+   the pinned chrome meets the scrolling content, whatever the chrome holds.
+   `chromeDividers="scroll"` (the plain-pane default, no attribute) draws each only while
+   `wireScrollDividers` reports content scrolled away beneath it through
+   `data-scroll-divider` on the slot; a sunken pane defaults to `always`, which
+   draws both; `none` draws neither. The
+   line is an inset shadow inside the slot, so showing or hiding it never
+   moves the chrome or the content. */
+.kui-pane > :is(.kui-pane__header, .kui-pane__toolbar, .kui-pane__footer) {
+  --_kui-pane-chrome-divider: transparent;
+}
+
+.kui-pane > :is(.kui-pane__header, .kui-pane__toolbar) {
+  box-shadow: inset 0 -1px var(--_kui-pane-chrome-divider);
+}
+
+.kui-pane > .kui-pane__footer {
+  box-shadow: inset 0 1px var(--_kui-pane-chrome-divider);
+}
+
+.kui-pane:not([data-chrome-dividers])
+  > :is(.kui-pane__header, .kui-pane__toolbar)[data-scroll-divider*="b"],
+.kui-pane:not([data-chrome-dividers])
+  > .kui-pane__footer[data-scroll-divider*="t"],
+.kui-pane[data-chrome-dividers="always"]
+  > :is(.kui-pane__header, .kui-pane__toolbar, .kui-pane__footer) {
+  --_kui-pane-chrome-divider: var(
+    --kui-pane-separator-color,
+    var(--kui-color-neutral-border-normal)
+  );
+}
+
+/* `chromePlacement="auto"`: the header and footer stay pinned while the pane
+   is tall enough; below 480px of height (30rem, so it scales with the text
+   size) the whole pane scrolls as one column instead, so tall chrome can never
+   squeeze the content to nothing. The pane is its own size container and lays
+   its slots out as a column: while tall, the content fills the space between
+   the chrome and scrolls itself, and the pane never scrolls; while short, the
+   content takes its natural height and the pane scrolls. */
+.kui-pane[data-chrome-placement="auto"] {
+  container: kui-pane / size;
+  display: flex;
+  overflow-y: auto;
+  flex-direction: column;
+  overscroll-behavior: contain;
+}
+
+.kui-pane[data-chrome-placement="auto"]
+  > :is(.kui-pane__header, .kui-pane__footer) {
+  flex: none;
+}
+
+.kui-pane[data-chrome-placement="auto"] > .kui-pane__content {
+  flex: 1 1 0;
+}
+
+@container kui-pane (max-height: 30rem) {
+  .kui-pane[data-chrome-placement="auto"] > .kui-pane__content {
+    flex: none;
+    overflow: visible;
+  }
+}
+
+/* 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 Pane 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="pane"]: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);
+}
+
+/* As the only child of a NavStack view or a TabScaffold scene, a Pane fills
+   it too, so its content owns the scroll and its header and footer stay
+   pinned; the view or scene then never scrolls (it hands the Pane its
+   safe-area edge context, which the Pane's slots apply). */
+:is(.kui-nav-stack__view, .kui-tab-scaffold__scene)
+  > [data-component="pane"]:only-child {
+  height: 100%;
+}