vectis-ui 0.1.0 → 0.8.0

package/dist/components/VMenu/context.d.ts

@@ -1,10 +1,4 @@
 import { InjectionKey } from 'vue';
-/**
- * What the menu passes down to everything inside it. Choosing a command closes the
- * WHOLE menu, however deep in a submenu it was, and closing the outermost panel is
- * all it takes: the submenus are rendered inside it, and the browser closes a stack
- * of popovers from the outside in.
- */
 export interface MenuContext {
     closeAll: () => void;
 }
@@ -24,6 +18,8 @@ export declare const SUBMENU_HOVER_DELAY = 150;
  * access to.
  */
 export declare function menuInvoker(id: string): HTMLElement | null;
+/** The height of the rows: 32, 40 or 48 pixels. This is public API. */
+export type MenuSize = 'sm' | 'md' | 'lg';
 /** Where the menu itself may open, relative to its trigger. This is public API. */
 export type MenuPlacement = 'bottom-start' | 'bottom-end' | 'bottom' | 'top-start' | 'top-end' | 'top';
 /**

package/dist/components/VMenu/context.js.map

@@ -1 +1 @@
-{"version":3,"file":"context.js","names":[],"sources":["../../../src/components/VMenu/context.ts"],"sourcesContent":["import type { InjectionKey } from 'vue'\n\n/**\n * What the menu passes down to everything inside it. Choosing a command closes the\n * WHOLE menu, however deep in a submenu it was, and closing the outermost panel is\n * all it takes: the submenus are rendered inside it, and the browser closes a stack\n * of popovers from the outside in.\n */\nexport interface MenuContext {\n  closeAll: () => void\n}\n\nexport const menuKey: InjectionKey<MenuContext> = Symbol('v-menu')\n\n/**\n * How long the pointer must rest on an item before its submenu opens, and how long it\n * must stay away before it closes, in milliseconds. The wait is what stops every\n * panel crossed on the way elsewhere from flashing open.\n */\nexport const SUBMENU_HOVER_DELAY = 150\n\n// @a11y\n/**\n * Finds the element that opens a given panel — which is both what the panel positions\n * itself against and where the focus must return when it closes.\n *\n * It is found by searching the document rather than kept as a reference, because the\n * outermost panel's trigger is rendered by the consumer, in a slot the panel has no\n * access to.\n */\nexport function menuInvoker(id: string): HTMLElement | null {\n  // @fallback\n  /*\n   * The id is ESCAPED rather than cleaned up the way VTabs does it. There the id is\n   * one we BUILD, so awkward characters can simply be dropped; here it is the panel's\n   * real `id` attribute — a generated one, whose prefix the consumer can set through\n   * `app.config.idPrefix` — and rewriting it would leave the selector looking for an\n   * element that does not exist.\n   *\n   * Escaping the two characters able to close the quoted string is enough, and it is\n   * deliberately NOT done with `CSS.escape`: jsdom provides no `CSS` object at all, so\n   * that call would throw in every unit test.\n   */\n  return document.querySelector(`[popovertarget=\"${id.replace(/[\"\\\\]/g, '\\\\$&')}\"]`)\n}\n\n/** Where the menu itself may open, relative to its trigger. This is public API. */\nexport type MenuPlacement =\n  'bottom-start' | 'bottom-end' | 'bottom' | 'top-start' | 'top-end' | 'top'\n\n/**\n * The same list plus the sideways placement submenus use. It is internal: a submenu's\n * position is not the consumer's to choose.\n */\nexport type MenuPanelPlacement = MenuPlacement | 'right-start'\n"],"mappings":";AAYA,IAAa,IAAqC,OAAO,QAAQ;AAkBjE,SAAgB,EAAY,GAAgC;CAa1D,OAAO,SAAS,cAAc,mBAAmB,EAAG,QAAQ,UAAU,MAAM,EAAE,GAAG;AACnF"}
+{"version":3,"file":"context.js","names":[],"sources":["../../../src/components/VMenu/context.ts"],"sourcesContent":["/**\n * What the menu passes down to everything inside it. Choosing a command closes the\n * WHOLE menu, however deep in a submenu it was, and closing the outermost panel is\n * all it takes: the submenus are rendered inside it, and the browser closes a stack\n * of popovers from the outside in.\n */\n\nimport type { InjectionKey } from 'vue'\n\nexport interface MenuContext {\n  closeAll: () => void\n}\n\nexport const menuKey: InjectionKey<MenuContext> = Symbol('v-menu')\n\n/**\n * How long the pointer must rest on an item before its submenu opens, and how long it\n * must stay away before it closes, in milliseconds. The wait is what stops every\n * panel crossed on the way elsewhere from flashing open.\n */\nexport const SUBMENU_HOVER_DELAY = 150\n\n// @a11y\n/**\n * Finds the element that opens a given panel — which is both what the panel positions\n * itself against and where the focus must return when it closes.\n *\n * It is found by searching the document rather than kept as a reference, because the\n * outermost panel's trigger is rendered by the consumer, in a slot the panel has no\n * access to.\n */\nexport function menuInvoker(id: string): HTMLElement | null {\n  // @fallback\n  /*\n   * The id is ESCAPED rather than cleaned up the way VTabs does it. There the id is\n   * one we BUILD, so awkward characters can simply be dropped; here it is the panel's\n   * real `id` attribute — a generated one, whose prefix the consumer can set through\n   * `app.config.idPrefix` — and rewriting it would leave the selector looking for an\n   * element that does not exist.\n   *\n   * Escaping the two characters able to close the quoted string is enough, and it is\n   * deliberately NOT done with `CSS.escape`: jsdom provides no `CSS` object at all, so\n   * that call would throw in every unit test.\n   */\n  return document.querySelector(`[popovertarget=\"${id.replace(/[\"\\\\]/g, '\\\\$&')}\"]`)\n}\n\n/** The height of the rows: 32, 40 or 48 pixels. This is public API. */\nexport type MenuSize = 'sm' | 'md' | 'lg'\n\n/** Where the menu itself may open, relative to its trigger. This is public API. */\nexport type MenuPlacement =\n  'bottom-start' | 'bottom-end' | 'bottom' | 'top-start' | 'top-end' | 'top'\n\n/**\n * The same list plus the sideways placement submenus use. It is internal: a submenu's\n * position is not the consumer's to choose.\n */\nexport type MenuPanelPlacement = MenuPlacement | 'right-start'\n"],"mappings":";AAaA,IAAa,IAAqC,OAAO,QAAQ;AAkBjE,SAAgB,EAAY,GAAgC;CAa1D,OAAO,SAAS,cAAc,mBAAmB,EAAG,QAAQ,UAAU,MAAM,EAAE,GAAG;AACnF"}

package/dist/components/VPagination/VPagination.css

@@ -1,2 +1,2 @@
 @layer vectis.reset, vectis.tokens, vectis.components, vectis.utilities;
-@layer vectis.components{.v-pagination{display:flex}.v-pagination[data-responsive]{container:v-pagination/inline-size}.v-pagination[data-align=center]{justify-content:center}.v-pagination[data-align=end]{justify-content:flex-end}.v-pagination-items{align-items:center;gap:var(--vectis-space-1);display:inline-flex}.v-button-group.v-pagination-items{gap:0}.v-pagination-page[data-size]{min-inline-size:var(--control-height);padding-inline:var(--vectis-space-2);transition:none}.v-pagination-ellipsis{cursor:default}[dir=rtl] .v-pagination-control .v-icon{scale:-1 1}@container v-pagination (width<=36rem){.v-pagination[data-responsive] .v-pagination-page[data-distance="3"]{display:none}}@container v-pagination (width<=31rem){.v-pagination[data-responsive] .v-pagination-page[data-distance="2"],.v-pagination[data-responsive][data-controls-display=both] .v-pagination-control-label{display:none}}@container v-pagination (width<=25rem){.v-pagination[data-responsive] .v-pagination-page[data-distance="1"]{display:none}}}
+@layer vectis.components{.v-pagination{display:flex}.v-pagination[data-responsive]{container:v-pagination/inline-size}.v-pagination[data-align=center]{justify-content:center}.v-pagination[data-align=end]{justify-content:flex-end}.v-pagination-page[data-size]{min-inline-size:var(--control-height);padding-inline:var(--vectis-space-2);transition:none}.v-pagination-ellipsis{cursor:default}@container v-pagination (width<=36rem){.v-pagination[data-responsive] .v-pagination-page[data-distance="3"]{display:none}}@container v-pagination (width<=31rem){.v-pagination[data-responsive] .v-pagination-page[data-distance="2"],.v-pagination[data-responsive][data-controls=both] .v-pagination-control-label{display:none}}@container v-pagination (width<=25rem){.v-pagination[data-responsive] .v-pagination-page[data-distance="1"]{display:none}}}

package/dist/components/VPagination/VPagination.d.ts

@@ -1,6 +1,24 @@
 import { IconSource } from '../VIcon/types.js';
+/** How the pages that are not the current one are drawn. */
+export type PaginationItemVariant = 'ghost' | 'outline';
+/** The colour of the current page. */
+export type PaginationTone = 'accent' | 'neutral' | 'danger';
+/** The height of the pills, from the scale every control shares. */
+export type PaginationSize = 'xs' | 'sm' | 'md' | 'lg' | 'xl';
+/** Where the row sits in the width it is given. */
+export type PaginationAlign = 'start' | 'center' | 'end';
+/** Whether the previous and next controls are rendered, and what they show. */
+export type PaginationControls = false | 'icon' | 'text' | 'both';
+/**
+ * Which pages cannot be reached, given either as a list of page numbers or as a function
+ * answering that question for a page.
+ */
+export type PaginationMatcher = number[] | ((page: number) => boolean);
 interface PaginationProps {
-    /** How many pages there are in all. */
+    /**
+     * How many pages there are in all. It is 1 by default, which renders a single page: the
+     * real count almost always has to be given.
+     */
     length?: number;
     /**
      * How many slots to render, ellipses counted among them — so the row keeps exactly
@@ -9,28 +27,46 @@ interface PaginationProps {
      * page is rendered.
      */
     totalVisible?: number;
-    /** Joins every button into one segmented control. */
-    attached?: boolean;
     /**
-     * How the pages OTHER than the current one, and the controls, are drawn. The current
-     * page is always filled, whatever this says.
+     * Separates the buttons instead of joining them into one segmented control. It is the
+     * word VButtonGroup and VToggle use for the same question, in the same direction.
+     */
+    detached?: boolean;
+    /**
+     * Takes the lines out from between the joined buttons, so the row reads as one frame rather
+     * than as segments, on the terms of VButtonGroup's own `seamless`. It has no effect under
+     * `detached`.
+     */
+    seamless?: boolean;
+    /**
+     * How the pages OTHER than the current one, and the controls, are drawn. The current page
+     * is always filled, whatever this says. It is named for the ITEMS because that is what it
+     * paints: on VTabs and VDataTable `variant` names the decoration of the frame instead.
      */
-    variant?: 'ghost' | 'outline';
+    itemVariant?: PaginationItemVariant;
     /** The colour the current page takes. The other pages and the controls stay neutral. */
-    tone?: 'accent' | 'neutral' | 'danger';
+    tone?: PaginationTone;
     /** The height of the buttons, from the scale shared by every control. */
-    size?: 'xs' | 'sm' | 'md' | 'lg' | 'xl';
+    size?: PaginationSize;
     /** Takes 4px off the height of every button. */
     compact?: boolean;
+    /**
+     * Raises the row off the page, on the terms of VButton's own `elevated`. Joined, the
+     * shadow belongs to the ROW and not to each pill, which is what stops it falling into
+     * the joints; detached, every button carries its own.
+     */
+    elevated?: boolean;
     /**
      * Where the row sits in the space it is given. It only matters in responsive mode,
      * where the row takes the whole width available.
      */
-    align?: 'start' | 'center' | 'end';
-    /** Shows the previous and next buttons on either side of the pages. */
-    showControls?: boolean;
-    /** Whether those controls show an icon, their label, or both. */
-    controlsDisplay?: 'icon' | 'text' | 'both';
+    align?: PaginationAlign;
+    /**
+     * The previous and next buttons on either side of the pages: what they show, or `false`
+     * to leave them out. One prop rather than two, the shape VFilePicker's `preview` and
+     * VCarousel's `controls` already use.
+     */
+    controls?: PaginationControls;
     /** The icon of the previous control: an icon name, or an explicit render. */
     prevIcon?: IconSource;
     /** The icon of the next control: an icon name, or an explicit render. */
@@ -51,7 +87,7 @@ interface PaginationProps {
      * Which pages cannot be reached, as a list or as a function. The previous and next
      * controls step OVER them rather than stopping at one.
      */
-    disabledPages?: number[] | ((page: number) => boolean);
+    disabledPages?: PaginationMatcher;
     /**
      * Lets the row shed pages as the space narrows, by asking about its own width. It is
      * off by default, because it makes the row take the full width available.
@@ -71,6 +107,7 @@ interface PaginationProps {
 }
 type __VLS_Props = PaginationProps;
 type __VLS_ModelProps = {
+    /** The page being shown, counted from 1. It starts on the first. */
     modelValue?: number;
 };
 type __VLS_PublicProps = __VLS_Props & __VLS_ModelProps;
@@ -80,22 +117,23 @@ declare const __VLS_export: import('vue').DefineComponent<__VLS_PublicProps, {},
     "onUpdate:modelValue"?: ((value: number) => any) | undefined;
 }>, {
     label: string;
-    size: "xs" | "sm" | "md" | "lg" | "xl";
+    size: PaginationSize;
     length: number;
-    variant: "ghost" | "outline";
-    tone: "accent" | "neutral" | "danger";
+    tone: PaginationTone;
+    elevated: boolean;
     compact: boolean;
     disabled: boolean;
+    detached: boolean;
+    seamless: boolean;
     totalVisible: number;
-    attached: boolean;
-    align: "start" | "center" | "end";
-    showControls: boolean;
-    controlsDisplay: "icon" | "text" | "both";
+    itemVariant: PaginationItemVariant;
+    align: PaginationAlign;
+    controls: PaginationControls;
     prevIcon: IconSource;
     nextIcon: IconSource;
     prevLabel: string;
     nextLabel: string;
-    disabledPages: number[] | ((page: number) => boolean);
+    disabledPages: PaginationMatcher;
     responsive: boolean;
     pageLabel: (page: number) => string;
 }, {}, {}, {}, string, import('vue').ComponentProvideOptions, false, {}, any>;

package/dist/components/VPagination/VPagination.js.map

@@ -1 +1 @@
-{"version":3,"file":"VPagination.js","names":[],"sources":["../../../src/components/VPagination/VPagination.vue"],"sourcesContent":["<script setup lang=\"ts\">\n// @keyboard @core\n/**\n * The row of page numbers under a long list. Every pill is a VButton and the previous\n * and next controls are buttons too, so nothing about hovering, focusing or disabling\n * is written again here.\n *\n * A long list has more pages than fit on a line, and the row deals with that TWICE,\n * for two different reasons. First logically: `totalVisible` fixes how many slots are\n * rendered at all, and the pages that do not fit are replaced by an ellipsis — pure\n * arithmetic, identical on the server and in the browser. Then visually: as the space\n * actually available narrows, the neighbours of the current page are hidden one step\n * at a time, and that half is entirely CSS, the row asking about its own width rather\n * than being measured from code.\n *\n * The only behavioural JavaScript is the keyboard, explained where it is written.\n */\nimport { computed, ref } from 'vue'\n\nimport VButton from '../VButton/VButton.vue'\nimport VButtonGroup from '../VButton/VButtonGroup.vue'\nimport VIcon from '../VIcon/VIcon.vue'\nimport { iconProps } from '../VIcon/iconProps'\nimport { chevron_left as chevronLeftIcon } from '../VIcon/icons/chevron_left'\nimport { chevron_right as chevronRightIcon } from '../VIcon/icons/chevron_right'\nimport { more_horiz as moreHorizIcon } from '../VIcon/icons/more_horiz'\nimport type { IconSource } from '../VIcon/types'\nimport VIconButton from '../VIconButton/VIconButton.vue'\n\nimport { arrowNavigate, navigableItems } from '../../utils/arrowNav'\nimport { clamp } from '../../utils/number'\nimport { resolveMatcher } from '../../utils/matcher'\n\nimport { useAriaLabel } from '../../composables/useAriaLabel'\nimport { useMessages } from '../../i18n/state'\n\ninterface PaginationProps {\n  /** How many pages there are in all. */\n  length?: number\n  /**\n   * How many slots to render, ellipses counted among them — so the row keeps exactly\n   * the same width whichever page is current. Below five there would be nothing left\n   * to show around the current page, so five is the effective minimum. Left out, every\n   * page is rendered.\n   */\n  totalVisible?: number\n\n  /** Joins every button into one segmented control. */\n  attached?: boolean\n  /**\n   * How the pages OTHER than the current one, and the controls, are drawn. The current\n   * page is always filled, whatever this says.\n   */\n  variant?: 'ghost' | 'outline'\n  /** The colour the current page takes. The other pages and the controls stay neutral. */\n  tone?: 'accent' | 'neutral' | 'danger'\n  /** The height of the buttons, from the scale shared by every control. */\n  size?: 'xs' | 'sm' | 'md' | 'lg' | 'xl'\n  /** Takes 4px off the height of every button. */\n  compact?: boolean\n  /**\n   * Where the row sits in the space it is given. It only matters in responsive mode,\n   * where the row takes the whole width available.\n   */\n  align?: 'start' | 'center' | 'end'\n\n  /** Shows the previous and next buttons on either side of the pages. */\n  showControls?: boolean\n  /** Whether those controls show an icon, their label, or both. */\n  controlsDisplay?: 'icon' | 'text' | 'both'\n  /** The icon of the previous control: an icon name, or an explicit render. */\n  prevIcon?: IconSource\n  /** The icon of the next control: an icon name, or an explicit render. */\n  nextIcon?: IconSource\n  /**\n   * The wording of the previous control, used both as its visible text and as what\n   * screen readers announce. It falls back to the design system dictionary.\n   */\n  prevLabel?: string\n  /**\n   * The wording of the next control, used both as its visible text and as what screen\n   * readers announce. It falls back to the design system dictionary.\n   */\n  nextLabel?: string\n\n  /** Makes the whole component unusable. */\n  disabled?: boolean\n  /**\n   * Which pages cannot be reached, as a list or as a function. The previous and next\n   * controls step OVER them rather than stopping at one.\n   */\n  disabledPages?: number[] | ((page: number) => boolean)\n\n  /**\n   * Lets the row shed pages as the space narrows, by asking about its own width. It is\n   * off by default, because it makes the row take the full width available.\n   */\n  responsive?: boolean\n\n  /**\n   * What screen readers announce for the navigation itself. It falls back to the\n   * design system dictionary.\n   */\n  label?: string\n  /**\n   * How a page is announced. A pill shows a bare number, which alone means nothing to\n   * a screen reader — this is what turns it into \"Page 3\". It falls back to the design\n   * system dictionary.\n   */\n  pageLabel?: (page: number) => string\n}\n\nconst props = withDefaults(defineProps<PaginationProps>(), {\n  length: 1,\n  totalVisible: undefined,\n  attached: false,\n  variant: 'ghost',\n  tone: 'accent',\n  size: 'md',\n  compact: false,\n  align: 'start',\n  showControls: true,\n  controlsDisplay: 'icon',\n  prevIcon: () => chevronLeftIcon,\n  nextIcon: () => chevronRightIcon,\n  prevLabel: undefined,\n  nextLabel: undefined,\n  disabled: false,\n  disabledPages: undefined,\n  responsive: false,\n  label: undefined,\n  pageLabel: undefined,\n})\n\n// The prop wins over the dictionary, and above both, a consumer's own aria-label or\n// aria-labelledby still wins — that arbitration is what `useAriaLabel` is for.\nconst m = useMessages()\nconst ariaLabel = useAriaLabel(() => props.label ?? m.value.pagination.label)\nconst resolvedPrevLabel = computed(() => props.prevLabel ?? m.value.pagination.previous)\nconst resolvedNextLabel = computed(() => props.nextLabel ?? m.value.pagination.next)\n\nconst page = defineModel<number>({ default: 1 })\n\n/** One slot in the row: either a page, or the ellipsis standing for those left out. */\ntype PaginationItem =\n  | { kind: 'page'; key: string; page: number; edge: boolean; distance: number }\n  | { kind: 'gap'; key: string }\n\nconst total = computed(() => Math.max(Math.trunc(props.length), 1))\nconst currentPage = computed(() => clamp(page.value, 1, total.value))\n\nconst isPageDisabled = computed(() => resolveMatcher(props.disabledPages))\n\n// @a11y — a pill shows nothing but a number, which on its own tells a screen reader\n// nothing at all; this is what has it announced as \"Page 3\".\nfunction pageLabelFor(n: number): string {\n  return props.pageLabel ? props.pageLabel(n) : m.value.pagination.page(n)\n}\n\n/**\n * Works out which slots the row holds.\n *\n * The count is CONSTANT: `totalVisible` counts everything rendered, the ellipses\n * included, so the row never changes width as one moves through the pages. The window\n * of pages around the current one is centred on it, and near either end it SHIFTS\n * rather than shrinking — which is what keeps that count constant there too.\n *\n * Each page also carries how far it is from the current one. That distance is what the\n * responsive hiding sorts by, and it is capped at three: past that, the most distant\n * neighbours all disappear together at the first step.\n */\nconst items = computed<PaginationItem[]>(() => {\n  const count = total.value\n  const current = currentPage.value\n\n  const pageItem = (n: number): PaginationItem => ({\n    kind: 'page',\n    key: `page-${n}`,\n    page: n,\n    edge: n === 1 || n === count,\n    distance: Math.min(Math.abs(n - current), 3),\n  })\n  const pages = (from: number, to: number): PaginationItem[] => {\n    const out: PaginationItem[] = []\n    for (let n = from; n <= to; n++) out.push(pageItem(n))\n    return out\n  }\n  // Keyed by the side it stands on, never by the page it follows: there is at most one\n  // ellipsis per side, and the left one always comes after the first page while the right\n  // one always comes before the last. A key derived from the window would change on every\n  // navigation, so the right-hand ellipsis would be destroyed and rebuilt each time the\n  // window slid, for a node that never changes.\n  const gap = (side: 'start' | 'end'): PaginationItem => ({ kind: 'gap', key: `gap-${side}` })\n\n  // With no limit given, nothing is left out. Below five slots there would be no room\n  // for the first page, an ellipsis, the current page, another ellipsis and the last,\n  // so that is the floor.\n  const visible =\n    props.totalVisible === undefined ? count : Math.max(Math.trunc(props.totalVisible), 5)\n  if (visible >= count) return pages(1, count)\n\n  const start = current - Math.floor((visible - 5) / 2)\n  const end = start + (visible - 5)\n\n  // Close to either end, an ellipsis on that side would stand for no missing page at\n  // all. The window is stretched to the bound instead, which both avoids that and\n  // keeps the number of slots exactly the same.\n  if (start <= 3) return [...pages(1, visible - 2), gap('end'), pageItem(count)]\n  if (end >= count - 2) return [pageItem(1), gap('start'), ...pages(count - visible + 3, count)]\n  return [pageItem(1), gap('start'), ...pages(start, end), gap('end'), pageItem(count)]\n})\n\n/**\n * Where a control leads: the nearest page in that direction that can actually be\n * reached, disabled ones being stepped over rather than stopped at.\n *\n * Answering `undefined` means there is none left, which disables the control — and\n * that single answer also covers being on the first or the last page, with no separate\n * test for the ends.\n */\nfunction step(direction: -1 | 1): number | undefined {\n  for (let n = currentPage.value + direction; n >= 1 && n <= total.value; n += direction) {\n    if (!isPageDisabled.value(n)) return n\n  }\n  return undefined\n}\n\nconst prevTarget = computed(() => step(-1))\nconst nextTarget = computed(() => step(1))\nconst prevDisabled = computed(() => props.disabled || prevTarget.value === undefined)\nconst nextDisabled = computed(() => props.disabled || nextTarget.value === undefined)\n\nfunction goTo(n: number | undefined) {\n  if (n === undefined) return\n  page.value = clamp(n, 1, total.value)\n}\n\nconst navEl = ref<HTMLElement | null>(null)\n\n// @keyboard @a11y\n/**\n * The arrow keys, through the shared implementation in `utils/arrowNav`. Tab is left\n * alone: every visible pill remains a stop in the tab order, as in any list of links.\n *\n * The pills the responsive rules have hidden are left out by the helper, which skips\n * anything not displayed — so they cannot be focused into.\n */\nfunction onKeydown(event: KeyboardEvent) {\n  const nav = navEl.value\n  if (!nav) return\n  arrowNavigate(event, nav, navigableItems(nav, '.v-pagination-page:not(:disabled)'))\n}\n</script>\n\n<template>\n  <nav\n    ref=\"navEl\"\n    class=\"v-pagination\"\n    :aria-label=\"ariaLabel\"\n    :data-align=\"align\"\n    :data-controls-display=\"controlsDisplay\"\n    :data-responsive=\"responsive ? '' : undefined\"\n    @keydown=\"onKeydown\"\n  >\n    <!-- Joined, the row is a VButtonGroup, which merges the borders of its DIRECT\n         button children. That is why there is no list markup wrapping the pills, and\n         why the ellipsis is itself an inert button rather than a plain span: anything\n         else between two pills would break the seam. -->\n    <component :is=\"attached ? VButtonGroup : 'div'\" class=\"v-pagination-items\">\n      <template v-if=\"showControls\">\n        <VIconButton\n          v-if=\"controlsDisplay === 'icon'\"\n          class=\"v-pagination-control\"\n          :label=\"resolvedPrevLabel\"\n          :variant=\"variant\"\n          tone=\"neutral\"\n          :size=\"size\"\n          :compact=\"compact\"\n          :disabled=\"prevDisabled\"\n          @click=\"goTo(prevTarget)\"\n        >\n          <VIcon v-bind=\"iconProps(prevIcon)\" />\n        </VIconButton>\n        <!-- The control is named explicitly even though its label is visible: at\n             narrow widths that label is hidden and only the icon remains, and the name\n             a screen reader announces has to survive that. -->\n        <VButton\n          v-else\n          class=\"v-pagination-control\"\n          :variant=\"variant\"\n          tone=\"neutral\"\n          :size=\"size\"\n          :compact=\"compact\"\n          :disabled=\"prevDisabled\"\n          :aria-label=\"resolvedPrevLabel\"\n          @click=\"goTo(prevTarget)\"\n        >\n          <template v-if=\"controlsDisplay === 'both'\" #start>\n            <VIcon v-bind=\"iconProps(prevIcon)\" />\n          </template>\n          <span class=\"v-pagination-control-label\">{{ resolvedPrevLabel }}</span>\n        </VButton>\n      </template>\n\n      <template v-for=\"item in items\" :key=\"item.key\">\n        <VButton\n          v-if=\"item.kind === 'page'\"\n          class=\"v-pagination-page\"\n          :variant=\"item.page === currentPage ? 'solid' : variant\"\n          :tone=\"item.page === currentPage ? tone : 'neutral'\"\n          :size=\"size\"\n          :compact=\"compact\"\n          :disabled=\"disabled || isPageDisabled(item.page)\"\n          :aria-label=\"pageLabelFor(item.page)\"\n          :aria-current=\"item.page === currentPage ? 'page' : undefined\"\n          :data-edge=\"item.edge ? '' : undefined\"\n          :data-distance=\"!item.edge && item.distance > 0 ? item.distance : undefined\"\n          @click=\"goTo(item.page)\"\n        >\n          {{ item.page }}\n        </VButton>\n        <!-- The ellipsis is a disabled button rather than a span: being a button, it\n             keeps the joined row's seam continuous and follows the size and density\n             like everything else. Disabling it takes it out of the tab order, and it\n             is hidden from screen readers, which have the page numbers themselves. -->\n        <VIconButton\n          v-else\n          class=\"v-pagination-ellipsis\"\n          :label=\"m.pagination.hiddenPages\"\n          aria-hidden=\"true\"\n          :variant=\"variant\"\n          tone=\"neutral\"\n          :size=\"size\"\n          :compact=\"compact\"\n          disabled\n        >\n          <VIcon :name=\"moreHorizIcon\" />\n        </VIconButton>\n      </template>\n\n      <template v-if=\"showControls\">\n        <VIconButton\n          v-if=\"controlsDisplay === 'icon'\"\n          class=\"v-pagination-control\"\n          :label=\"resolvedNextLabel\"\n          :variant=\"variant\"\n          tone=\"neutral\"\n          :size=\"size\"\n          :compact=\"compact\"\n          :disabled=\"nextDisabled\"\n          @click=\"goTo(nextTarget)\"\n        >\n          <VIcon v-bind=\"iconProps(nextIcon)\" />\n        </VIconButton>\n        <VButton\n          v-else\n          class=\"v-pagination-control\"\n          :variant=\"variant\"\n          tone=\"neutral\"\n          :size=\"size\"\n          :compact=\"compact\"\n          :disabled=\"nextDisabled\"\n          :aria-label=\"resolvedNextLabel\"\n          @click=\"goTo(nextTarget)\"\n        >\n          <template v-if=\"controlsDisplay === 'both'\" #end>\n            <VIcon v-bind=\"iconProps(nextIcon)\" />\n          </template>\n          <span class=\"v-pagination-control-label\">{{ resolvedNextLabel }}</span>\n        </VButton>\n      </template>\n    </component>\n  </nav>\n</template>\n\n<style>\n@layer vectis.components {\n  .v-pagination {\n    display: flex;\n  }\n\n  /*\n   * Making the row a query container is reserved for responsive mode, since every\n   * query below depends on it — and it is not free.\n   *\n   * A container of this kind computes its width WITHOUT looking at its content, so the\n   * row has to be block-level: as an inline box it would measure zero and hide\n   * everything at once. It therefore takes its parent's whole width, which is exactly\n   * what makes the hiding follow the space the component was actually given, and what\n   * obliges a flex parent to grant it one.\n   *\n   * Outside responsive mode the row keeps a width of its own and sits like any other\n   * content. Either way the alignment is asked for explicitly and never inferred.\n   */\n  .v-pagination[data-responsive] {\n    container-type: inline-size;\n    container-name: v-pagination;\n  }\n\n  .v-pagination[data-align='center'] {\n    justify-content: center;\n  }\n\n  .v-pagination[data-align='end'] {\n    justify-content: flex-end;\n  }\n\n  .v-pagination-items {\n    display: inline-flex;\n    align-items: center;\n    gap: var(--vectis-space-1);\n  }\n\n  /* Joined, the gap goes: VButtonGroup pulls the buttons onto one another itself. */\n  .v-button-group.v-pagination-items {\n    gap: 0;\n  }\n\n  /* Qualified by an attribute VButton always renders, which is what makes both of these\n     beat that button's own padding and its own transition whatever order the two sheets\n     end up in — the VIconButton idiom. */\n  .v-pagination-page[data-size] {\n    /* A one-digit pill is square, and widens by itself past that. The height variable\n       is set by the shared size class on this very element, so this single rule covers\n       all five sizes and their compact forms. */\n    min-inline-size: var(--control-height);\n    padding-inline: var(--vectis-space-2);\n\n    /*\n     * The current page changes appearance instantly, and that is deliberate: VButton\n     * fades `background-color` and `color` over `--vectis-duration-fast`, which is right\n     * for a button that stays put, and wrong here. Truncation SHIFTS its window, so from\n     * one page to the next the highlight keeps its slot but changes ELEMENT — the pill\n     * that was current fades out while its neighbour fades in, over the very same\n     * 120 ms. Delete this line and two adjacent pills are half-tinted for a few frames,\n     * which reads as a flicker; nothing in the console says a word about it.\n     *\n     * No duration avoids that: a symmetric fade overlaps, and an asymmetric one either\n     * leaves the row with no highlight at all or lets the outgoing pill trail at full\n     * strength behind the new one. Keeping the fade for hover alone is not expressible\n     * either — a transition is resolved from the state being entered, and the pill\n     * losing the highlight enters \"neither current nor hovered\", the exact state of a\n     * pill the pointer has just left. So the hover fade goes with it, on the pills only:\n     * the previous and next controls never change active state and keep theirs.\n     */\n    transition: none;\n  }\n\n  /* The ellipsis is a disabled button only as a technical device; to the reader it is\n     not a control that has been turned off, so it does not take the forbidden\n     cursor. */\n  .v-pagination-ellipsis {\n    cursor: default;\n  }\n\n  /* A chevron points at a physical direction, which the logical properties do not\n     mirror: in a right-to-left page it has to be flipped by hand. */\n  [dir='rtl'] .v-pagination-control .v-icon {\n    scale: -1 1;\n  }\n\n  /*\n   * The responsive half of the truncation. The row asks about ITS OWN width, so the\n   * steps follow the space the component was given rather than the size of the window\n   * — a sidebar and a full-width page behave differently, as they should, and nothing\n   * has to be measured from code.\n   *\n   * The thresholds are written as literal lengths because a container query accepts no\n   * variables. They are calibrated on the default size: there, a pill and a control are\n   * each one control height wide, 2.5rem, plus a 0.25rem gutter, so 2.75rem apiece — a\n   * thirteen-slot row needs about 35.5rem, eleven about 30, nine about 24.5, hence the\n   * three thresholds with a little margin. For the extreme cases, the biggest size or\n   * five-digit page numbers, the way out is `totalVisible` or turning this off.\n   *\n   * Each threshold is the width NEEDED to show that level, and not what remains once\n   * something is hidden: written the other way round, the row would overflow for the\n   * whole interval before the next step took effect.\n   *\n   * The most distant neighbours go first. The first and last pages, and the current\n   * one, carry no distance at all, so no rule here can ever reach them. Hiding them\n   * outright also takes them out of the tab order and out of the accessibility tree,\n   * which is intended: a control nobody can see should not be reachable.\n   *\n   * No ellipsis is added in place of a hidden neighbour — it is exactly as wide as the\n   * pill it would replace, so it would free nothing.\n   */\n  @container v-pagination (max-width: 36rem) {\n    .v-pagination[data-responsive] .v-pagination-page[data-distance='3'] {\n      display: none;\n    }\n  }\n\n  @container v-pagination (max-width: 31rem) {\n    .v-pagination[data-responsive] .v-pagination-page[data-distance='2'] {\n      display: none;\n    }\n\n    /* A control showing both its icon and its label is about four times as wide as a\n       pill, so dropping its label frees more room than sacrificing another page —\n       which is why it happens before the last step. It is never done when the control\n       shows text alone: there would be nothing left to click. */\n    .v-pagination[data-responsive][data-controls-display='both'] .v-pagination-control-label {\n      display: none;\n    }\n  }\n\n  @container v-pagination (max-width: 25rem) {\n    .v-pagination[data-responsive] .v-pagination-page[data-distance='1'] {\n      display: none;\n    }\n  }\n}\n</style>\n"],"mappings":""}
+{"version":3,"file":"VPagination.js","names":[],"sources":["../../../src/components/VPagination/VPagination.vue"],"sourcesContent":["<script setup lang=\"ts\">\n// @keyboard @core\n/**\n * The row of page numbers under a long list. Every pill is a VButton and the previous\n * and next controls are buttons too, so nothing about hovering, focusing or disabling\n * is written again here.\n *\n * A long list has more pages than fit on a line, and the row deals with that TWICE,\n * for two different reasons. First logically: `totalVisible` fixes how many slots are\n * rendered at all, and the pages that do not fit are replaced by an ellipsis — pure\n * arithmetic, identical on the server and in the browser. Then visually: as the space\n * actually available narrows, the neighbours of the current page are hidden one step\n * at a time, and that half is entirely CSS, the row asking about its own width rather\n * than being measured from code.\n *\n * The only behavioural JavaScript is the keyboard, explained where it is written.\n */\nimport { computed, h, ref } from 'vue'\nimport type { FunctionalComponent } from 'vue'\n\nimport VButton from '../VButton/VButton.vue'\nimport VButtonGroup from '../VButton/VButtonGroup.vue'\nimport VIcon from '../VIcon/VIcon.vue'\nimport { iconProps } from '../VIcon/iconProps'\nimport { chevron_left as chevronLeftIcon } from '../VIcon/icons/chevron_left'\nimport { chevron_right as chevronRightIcon } from '../VIcon/icons/chevron_right'\nimport { more_horiz as moreHorizIcon } from '../VIcon/icons/more_horiz'\nimport type { IconSource } from '../VIcon/types'\nimport VIconButton from '../VIconButton/VIconButton.vue'\n\nimport { arrowNavigate, navigableItems } from '../../utils/arrowNav'\nimport { clamp } from '../../utils/number'\nimport { resolveMatcher } from '../../utils/matcher'\n\nimport { useAriaLabel } from '../../composables/useAriaLabel'\nimport { useMessages } from '../../i18n/state'\n\n/** How the pages that are not the current one are drawn. */\nexport type PaginationItemVariant = 'ghost' | 'outline'\n\n/** The colour of the current page. */\nexport type PaginationTone = 'accent' | 'neutral' | 'danger'\n\n/** The height of the pills, from the scale every control shares. */\nexport type PaginationSize = 'xs' | 'sm' | 'md' | 'lg' | 'xl'\n\n/** Where the row sits in the width it is given. */\nexport type PaginationAlign = 'start' | 'center' | 'end'\n\n/** Whether the previous and next controls are rendered, and what they show. */\nexport type PaginationControls = false | 'icon' | 'text' | 'both'\n\n/**\n * Which pages cannot be reached, given either as a list of page numbers or as a function\n * answering that question for a page.\n */\nexport type PaginationMatcher = number[] | ((page: number) => boolean)\n\ninterface PaginationProps {\n  /**\n   * How many pages there are in all. It is 1 by default, which renders a single page: the\n   * real count almost always has to be given.\n   */\n  length?: number\n  /**\n   * How many slots to render, ellipses counted among them — so the row keeps exactly\n   * the same width whichever page is current. Below five there would be nothing left\n   * to show around the current page, so five is the effective minimum. Left out, every\n   * page is rendered.\n   */\n  totalVisible?: number\n\n  /**\n   * Separates the buttons instead of joining them into one segmented control. It is the\n   * word VButtonGroup and VToggle use for the same question, in the same direction.\n   */\n  detached?: boolean\n  /**\n   * Takes the lines out from between the joined buttons, so the row reads as one frame rather\n   * than as segments, on the terms of VButtonGroup's own `seamless`. It has no effect under\n   * `detached`.\n   */\n  seamless?: boolean\n  /**\n   * How the pages OTHER than the current one, and the controls, are drawn. The current page\n   * is always filled, whatever this says. It is named for the ITEMS because that is what it\n   * paints: on VTabs and VDataTable `variant` names the decoration of the frame instead.\n   */\n  itemVariant?: PaginationItemVariant\n  /** The colour the current page takes. The other pages and the controls stay neutral. */\n  tone?: PaginationTone\n  /** The height of the buttons, from the scale shared by every control. */\n  size?: PaginationSize\n  /** Takes 4px off the height of every button. */\n  compact?: boolean\n  /**\n   * Raises the row off the page, on the terms of VButton's own `elevated`. Joined, the\n   * shadow belongs to the ROW and not to each pill, which is what stops it falling into\n   * the joints; detached, every button carries its own.\n   */\n  elevated?: boolean\n  /**\n   * Where the row sits in the space it is given. It only matters in responsive mode,\n   * where the row takes the whole width available.\n   */\n  align?: PaginationAlign\n\n  /**\n   * The previous and next buttons on either side of the pages: what they show, or `false`\n   * to leave them out. One prop rather than two, the shape VFilePicker's `preview` and\n   * VCarousel's `controls` already use.\n   */\n  controls?: PaginationControls\n  /** The icon of the previous control: an icon name, or an explicit render. */\n  prevIcon?: IconSource\n  /** The icon of the next control: an icon name, or an explicit render. */\n  nextIcon?: IconSource\n  /**\n   * The wording of the previous control, used both as its visible text and as what\n   * screen readers announce. It falls back to the design system dictionary.\n   */\n  prevLabel?: string\n  /**\n   * The wording of the next control, used both as its visible text and as what screen\n   * readers announce. It falls back to the design system dictionary.\n   */\n  nextLabel?: string\n\n  /** Makes the whole component unusable. */\n  disabled?: boolean\n  /**\n   * Which pages cannot be reached, as a list or as a function. The previous and next\n   * controls step OVER them rather than stopping at one.\n   */\n  disabledPages?: PaginationMatcher\n\n  /**\n   * Lets the row shed pages as the space narrows, by asking about its own width. It is\n   * off by default, because it makes the row take the full width available.\n   */\n  responsive?: boolean\n\n  /**\n   * What screen readers announce for the navigation itself. It falls back to the\n   * design system dictionary.\n   */\n  label?: string\n  /**\n   * How a page is announced. A pill shows a bare number, which alone means nothing to\n   * a screen reader — this is what turns it into \"Page 3\". It falls back to the design\n   * system dictionary.\n   */\n  pageLabel?: (page: number) => string\n}\n\nconst props = withDefaults(defineProps<PaginationProps>(), {\n  length: 1,\n  totalVisible: undefined,\n  detached: false,\n  seamless: false,\n  itemVariant: 'ghost',\n  tone: 'accent',\n  size: 'md',\n  compact: false,\n  elevated: false,\n  align: 'start',\n  controls: 'icon',\n  prevIcon: () => chevronLeftIcon,\n  nextIcon: () => chevronRightIcon,\n  prevLabel: undefined,\n  nextLabel: undefined,\n  disabled: false,\n  disabledPages: undefined,\n  responsive: false,\n  label: undefined,\n  pageLabel: undefined,\n})\n\n// The prop wins over the dictionary, and above both, a consumer's own aria-label or\n// aria-labelledby still wins — that arbitration is what `useAriaLabel` is for.\nconst m = useMessages()\nconst ariaLabel = useAriaLabel(() => props.label ?? m.value.pagination.label)\nconst resolvedPrevLabel = computed(() => props.prevLabel ?? m.value.pagination.previous)\nconst resolvedNextLabel = computed(() => props.nextLabel ?? m.value.pagination.next)\n\n/** The page being shown, counted from 1. It starts on the first. */\nconst page = defineModel<number>({ default: 1 })\n\n/** One slot in the row: either a page, or the ellipsis standing for those left out. */\ntype PaginationItem =\n  | { kind: 'page'; key: string; page: number; edge: boolean; distance: number }\n  | { kind: 'gap'; key: string }\n\nconst total = computed(() => Math.max(Math.trunc(props.length), 1))\nconst currentPage = computed(() => clamp(page.value, 1, total.value))\n\nconst isPageDisabled = computed(() => resolveMatcher(props.disabledPages))\n\n// @a11y — a pill shows nothing but a number, which on its own tells a screen reader\n// nothing at all; this is what has it announced as \"Page 3\".\nfunction pageLabelFor(n: number): string {\n  return props.pageLabel ? props.pageLabel(n) : m.value.pagination.page(n)\n}\n\n/**\n * Works out which slots the row holds.\n *\n * The count is CONSTANT: `totalVisible` counts everything rendered, the ellipses\n * included, so the row never changes width as one moves through the pages. The window\n * of pages around the current one is centred on it, and near either end it SHIFTS\n * rather than shrinking — which is what keeps that count constant there too.\n *\n * Each page also carries how far it is from the current one. That distance is what the\n * responsive hiding sorts by, and it is capped at three: past that, the most distant\n * neighbours all disappear together at the first step.\n */\nconst items = computed<PaginationItem[]>(() => {\n  const count = total.value\n  const current = currentPage.value\n\n  const pageItem = (n: number): PaginationItem => ({\n    kind: 'page',\n    key: `page-${n}`,\n    page: n,\n    edge: n === 1 || n === count,\n    distance: Math.min(Math.abs(n - current), 3),\n  })\n  const pages = (from: number, to: number): PaginationItem[] => {\n    const out: PaginationItem[] = []\n    for (let n = from; n <= to; n++) out.push(pageItem(n))\n    return out\n  }\n  // Keyed by the side it stands on, never by the page it follows: there is at most one\n  // ellipsis per side, and the left one always comes after the first page while the right\n  // one always comes before the last. A key derived from the window would change on every\n  // navigation, so the right-hand ellipsis would be destroyed and rebuilt each time the\n  // window slid, for a node that never changes.\n  const gap = (side: 'start' | 'end'): PaginationItem => ({ kind: 'gap', key: `gap-${side}` })\n\n  // With no limit given, nothing is left out. Below five slots there would be no room\n  // for the first page, an ellipsis, the current page, another ellipsis and the last,\n  // so that is the floor.\n  const visible =\n    props.totalVisible === undefined ? count : Math.max(Math.trunc(props.totalVisible), 5)\n  if (visible >= count) return pages(1, count)\n\n  const start = current - Math.floor((visible - 5) / 2)\n  const end = start + (visible - 5)\n\n  // Close to either end, an ellipsis on that side would stand for no missing page at\n  // all. The window is stretched to the bound instead, which both avoids that and\n  // keeps the number of slots exactly the same.\n  if (start <= 3) return [...pages(1, visible - 2), gap('end'), pageItem(count)]\n  if (end >= count - 2) return [pageItem(1), gap('start'), ...pages(count - visible + 3, count)]\n  return [pageItem(1), gap('start'), ...pages(start, end), gap('end'), pageItem(count)]\n})\n\n/**\n * Where a control leads: the nearest page in that direction that can actually be\n * reached, disabled ones being stepped over rather than stopped at.\n *\n * Answering `undefined` means there is none left, which disables the control — and\n * that single answer also covers being on the first or the last page, with no separate\n * test for the ends.\n */\nfunction step(direction: -1 | 1): number | undefined {\n  for (let n = currentPage.value + direction; n >= 1 && n <= total.value; n += direction) {\n    if (!isPageDisabled.value(n)) return n\n  }\n  return undefined\n}\n\nconst prevTarget = computed(() => step(-1))\nconst nextTarget = computed(() => step(1))\nconst prevDisabled = computed(() => props.disabled || prevTarget.value === undefined)\nconst nextDisabled = computed(() => props.disabled || nextTarget.value === undefined)\n\nfunction goTo(n: number | undefined) {\n  if (n === undefined) return\n  page.value = clamp(n, 1, total.value)\n}\n\n/*\n * The previous and next controls, written ONCE: the two differ only by their direction, and\n * a pair of template blocks drifting apart on the next change is exactly what this avoids.\n * A functional component because the two sit at either end of the row, with the pages in\n * between, where a `v-for` over two descriptors could not put them.\n *\n * The icon goes on the side the control points to — before the word going back, after it\n * going forward — and every icon mirrors in a right-to-left page, an arrow pointing at a\n * physical direction.\n *\n * The control is named explicitly even though its label is visible: at narrow widths that\n * label is hidden and only the icon remains, and the name a screen reader announces has to\n * survive that.\n */\nconst PageControl: FunctionalComponent<{ side: 'prev' | 'next' }> = ({ side }) => {\n  const prev = side === 'prev'\n  const label = prev ? resolvedPrevLabel.value : resolvedNextLabel.value\n  const icon = prev ? props.prevIcon : props.nextIcon\n  const common = {\n    class: 'v-pagination-control',\n    variant: props.itemVariant,\n    disabled: prev ? prevDisabled.value : nextDisabled.value,\n    onClick: () => goTo(prev ? prevTarget.value : nextTarget.value),\n  }\n  const glyph = () => h(VIcon, { ...iconProps(icon), mirrored: true })\n  if (props.controls === 'icon') return h(VIconButton, { ...common, label }, glyph)\n  return h(\n    VButton,\n    { ...common, tone: 'neutral', 'aria-label': label },\n    {\n      ...(props.controls === 'both' ? { [prev ? 'start' : 'end']: glyph } : {}),\n      default: () => h('span', { class: 'v-pagination-control-label' }, label),\n    },\n  )\n}\n\nconst navEl = ref<HTMLElement | null>(null)\n\n// @keyboard @a11y\n/**\n * The arrow keys, through the shared implementation in `utils/arrowNav`. Tab is left\n * alone: every visible pill remains a stop in the tab order, as in any list of links.\n *\n * The pills the responsive rules have hidden are left out by the helper, which skips\n * anything not displayed — so they cannot be focused into.\n */\nfunction onKeydown(event: KeyboardEvent) {\n  const nav = navEl.value\n  if (!nav) return\n  arrowNavigate(event, nav, () => navigableItems(nav, '.v-pagination-page:not(:disabled)'))\n}\n</script>\n\n<template>\n  <nav\n    ref=\"navEl\"\n    class=\"v-pagination\"\n    :aria-label=\"ariaLabel\"\n    :data-align=\"align\"\n    :data-controls=\"controls || undefined\"\n    :data-responsive=\"responsive ? '' : undefined\"\n    @keydown=\"onKeydown\"\n  >\n    <!-- The row is a VButtonGroup either way: joined it merges the borders of its DIRECT\n         button children, and detached it spaces them, which is all this prop asks of it.\n         That is why there is no list markup wrapping the pills, and why the ellipsis is\n         itself an inert button rather than a plain span: anything else between two pills\n         would break the seam. -->\n    <!--\n      The size, the density and the elevation are handed to the GROUP, which gives them to\n      every button inside, rather than repeated on each child. The elevation has to be there\n      in any case, since that is where VButtonGroup draws it: joined, the row takes the shadow\n      and the segments give theirs up, or it would fall into every joint.\n\n      `|| undefined` keeps the group opinion-free when the row does not ask, `undefined`\n      being what means \"no opinion\" there where `false` is an order. The size is always an\n      opinion, the pagination having a default of its own.\n    -->\n    <VButtonGroup\n      class=\"v-pagination-items\"\n      :detached=\"detached\"\n      :seamless=\"seamless\"\n      :size=\"size\"\n      :compact=\"compact || undefined\"\n      :elevated=\"elevated || undefined\"\n    >\n      <PageControl v-if=\"controls\" side=\"prev\" />\n\n      <template v-for=\"item in items\" :key=\"item.key\">\n        <VButton\n          v-if=\"item.kind === 'page'\"\n          class=\"v-pagination-page\"\n          :variant=\"item.page === currentPage ? 'solid' : itemVariant\"\n          :tone=\"item.page === currentPage ? tone : 'neutral'\"\n          :disabled=\"disabled || isPageDisabled(item.page)\"\n          :aria-label=\"pageLabelFor(item.page)\"\n          :aria-current=\"item.page === currentPage ? 'page' : undefined\"\n          :data-edge=\"item.edge ? '' : undefined\"\n          :data-distance=\"!item.edge && item.distance > 0 ? item.distance : undefined\"\n          @click=\"goTo(item.page)\"\n        >\n          {{ item.page }}\n        </VButton>\n        <!-- The ellipsis is a disabled icon-only button rather than a span: being a button,\n             it keeps the joined row's seam continuous and follows the size and density like\n             everything else. Disabling it takes it out of the tab order, and it is hidden\n             from screen readers, which have the page numbers themselves — which is also why\n             it is a VButton and not a VIconButton, whose required label would name something\n             nobody can reach. -->\n        <VButton\n          v-else\n          class=\"v-pagination-ellipsis\"\n          aria-hidden=\"true\"\n          data-icon-only\n          :variant=\"itemVariant\"\n          tone=\"neutral\"\n          disabled\n        >\n          <template #start>\n            <VIcon :name=\"moreHorizIcon\" />\n          </template>\n        </VButton>\n      </template>\n\n      <PageControl v-if=\"controls\" side=\"next\" />\n    </VButtonGroup>\n  </nav>\n</template>\n\n<style>\n@layer vectis.components {\n  .v-pagination {\n    display: flex;\n  }\n\n  /*\n   * Making the row a query container is reserved for responsive mode, since every\n   * query below depends on it — and it is not free.\n   *\n   * A container of this kind computes its width WITHOUT looking at its content, so the\n   * row has to be block-level: as an inline box it would measure zero and hide\n   * everything at once. It therefore takes its parent's whole width, which is exactly\n   * what makes the hiding follow the space the component was actually given, and what\n   * obliges a flex parent to grant it one.\n   *\n   * Outside responsive mode the row keeps a width of its own and sits like any other\n   * content. Either way the alignment is asked for explicitly and never inferred.\n   */\n  .v-pagination[data-responsive] {\n    container-type: inline-size;\n    container-name: v-pagination;\n  }\n\n  .v-pagination[data-align='center'] {\n    justify-content: center;\n  }\n\n  .v-pagination[data-align='end'] {\n    justify-content: flex-end;\n  }\n\n  /* Qualified by an attribute VButton always renders, which is what makes both of these\n     beat that button's own padding and its own transition whatever order the two sheets\n     end up in — the VIconButton idiom. */\n  .v-pagination-page[data-size] {\n    /* A one-digit pill is square, and widens by itself past that. The height variable\n       is set by the shared size class on this very element, so this single rule covers\n       all five sizes and their compact forms. */\n    min-inline-size: var(--control-height);\n    padding-inline: var(--vectis-space-2);\n\n    /*\n     * TRAP — the highlight changes instantly, and this must not be \"restored for\n     * consistency\". VButton fades `background-color` over `--vectis-duration-fast`, which is\n     * right for a button that stays put and wrong here: truncation SHIFTS its window, so from\n     * one page to the next the highlight keeps its slot but changes ELEMENT, and the outgoing\n     * and incoming pills are both half-tinted for a few frames — read as a flicker, with\n     * nothing in the console.\n     *\n     * No duration avoids it: symmetric fades overlap, asymmetric ones leave either no\n     * highlight or a trailing one. Keeping the fade for hover alone is not expressible\n     * either — a transition resolves from the state being ENTERED, and \"no longer current\"\n     * is the same state as \"no longer hovered\". So the hover fade goes too, on the pills\n     * only; the controls never change active state and keep theirs.\n     */\n    transition: none;\n  }\n\n  /* The ellipsis is a disabled button only as a technical device; to the reader it is\n     not a control that has been turned off, so it does not take the forbidden\n     cursor. */\n  .v-pagination-ellipsis {\n    cursor: default;\n  }\n\n  /*\n   * The responsive half of the truncation. The nav queries ITS OWN width, so the steps follow\n   * the space the component was given rather than the viewport — a sidebar and a full-width\n   * page behave differently, as they should, with nothing measured from code.\n   *\n   * The thresholds are rem LITERALS, a container query accepting no variables, and are\n   * calibrated on `md`: a pill and a control are each 2.5rem plus a 0.25rem gutter, so\n   * 2.75rem apiece — thirteen slots need ~35.5rem, eleven ~30, nine ~24.5, hence the three\n   * with a little margin. The extremes (the largest size, five-digit page numbers) are what\n   * `totalVisible` and `responsive: false` are for.\n   *\n   * Each threshold is the width NEEDED to show that level, never what remains after hiding:\n   * written the other way round the row overflows for the whole interval before the next\n   * step takes effect.\n   *\n   * The most distant neighbours go first. The edges and the current page carry no distance,\n   * so no rule here can reach them. `display: none` also takes a hidden pill out of the tab\n   * order and the a11y tree, which is intended. No ellipsis replaces one either — it is\n   * exactly as wide as the pill it would stand for, so it frees nothing.\n   */\n  @container v-pagination (max-width: 36rem) {\n    .v-pagination[data-responsive] .v-pagination-page[data-distance='3'] {\n      display: none;\n    }\n  }\n\n  @container v-pagination (max-width: 31rem) {\n    .v-pagination[data-responsive] .v-pagination-page[data-distance='2'] {\n      display: none;\n    }\n\n    /* A control showing both its icon and its label is about four times as wide as a\n       pill, so dropping its label frees more room than sacrificing another page —\n       which is why it happens before the last step. It is never done when the control\n       shows text alone: there would be nothing left to click. */\n    .v-pagination[data-responsive][data-controls='both'] .v-pagination-control-label {\n      display: none;\n    }\n  }\n\n  @container v-pagination (max-width: 25rem) {\n    .v-pagination[data-responsive] .v-pagination-page[data-distance='1'] {\n      display: none;\n    }\n  }\n}\n</style>\n"],"mappings":""}