vectis-ui 0.1.0

package/dist/components/VDatePicker/keyboard.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"keyboard.js","names":[],"sources":["../../../src/components/VDatePicker/keyboard.ts"],"sourcesContent":["// @keyboard @core\n/**\n * The pure half of VDatePicker's keyboard: it answers the single question \"how far\n * does this key move?\", and does nothing else. Actually moving the focus, calling\n * `preventDefault` and keeping the result inside the `min`/`max` bounds all stay in\n * the component, where the reactive state lives.\n *\n * It sits in VDatePicker's own folder rather than in `utils/` because it has exactly\n * one consumer, which fails the admission rule for shared code, and because\n * VDatePicker owns the contract (the same reasoning as `VHotkeys/platform.ts` and\n * `VCombobox/infiniteScroll.ts`). Being pure is also what makes this logic testable\n * without mounting anything: the handlers in the component only ever move DOM focus,\n * and jsdom lays nothing out to observe.\n *\n * One number has to be shared rather than repeated: `PICKER_COLUMNS` both cuts the\n * months and years grid into rows and defines what a vertical arrow steps over. Were\n * those two written as separate literals, widening the picker to four columns would\n * leave the arrows moving three cells, with no error anywhere to point at it.\n */\n\n/**\n * How many columns the months and years pickers are laid out in. It drives BOTH the\n * cutting of those grids into rows and the distance a vertical arrow travels: these\n * are the same number, and have to stay so.\n */\nexport const PICKER_COLUMNS = 3\n\nconst DAYS_PER_WEEK = 7\n\n/**\n * How far a key moves in the days view. It comes in two units because a month is not\n * a fixed number of days: `utils/date` provides one helper for each, and the caller\n * picks by looking at which shape it was handed.\n */\nexport type DayStep = { days: number } | { months: number }\n\n/**\n * The step a key produces in the days view, given the key itself, whether Shift is\n * held, and how far the focused date sits from the start of its week — the last\n * being what Home and End need in order to land on the right day. Returning\n * `undefined` means the key is none of this table's business, and the event must be\n * left alone.\n *\n * `weekdayOffset` is passed in rather than worked out here, because it depends on\n * which day the week starts on in the current locale, and resolving that belongs to\n * `utils/date`, not to a keyboard table.\n */\nexport function dayStep(\n  key: string,\n  shiftKey: boolean,\n  weekdayOffset: number,\n): DayStep | undefined {\n  switch (key) {\n    case 'ArrowRight':\n      return { days: 1 }\n    case 'ArrowLeft':\n      return { days: -1 }\n    case 'ArrowDown':\n      return { days: DAYS_PER_WEEK }\n    case 'ArrowUp':\n      return { days: -DAYS_PER_WEEK }\n    case 'Home':\n      // Negating an offset of zero yields `-0`, and the `|| 0` normalizes it back.\n      // `addDays` would not care either way, but a pure function should not hand out\n      // a value that `Object.is` reports as different from the zero every caller\n      // means.\n      return { days: -weekdayOffset || 0 }\n    case 'End':\n      return { days: DAYS_PER_WEEK - 1 - weekdayOffset }\n    case 'PageUp':\n      return { months: shiftKey ? -12 : -1 }\n    case 'PageDown':\n      return { months: shiftKey ? 12 : 1 }\n    default:\n      return undefined\n  }\n}\n\n/**\n * The step a key produces in the months and years views, expressed as a movement of\n * a flat index over a grid `PICKER_COLUMNS` wide. `undefined` again means the key is\n * not this table's business.\n *\n * Home and End are deliberately absent: both views are bounded — twelve months, a\n * year range fixed by `min` and `max` — and the component clamps whatever comes out,\n * so there is no wrapping behaviour left to define.\n */\nexport function gridDelta(key: string): number | undefined {\n  switch (key) {\n    case 'ArrowRight':\n      return 1\n    case 'ArrowLeft':\n      return -1\n    case 'ArrowDown':\n      return PICKER_COLUMNS\n    case 'ArrowUp':\n      return -PICKER_COLUMNS\n    default:\n      return undefined\n  }\n}\n"],"mappings":"AA+CA,SAAgB,EACd,GACA,GACA,GACqB;CACrB,QAAQ,GAAR;EACE,KAAK,cACH,OAAO,EAAE,MAAM,EAAE;EACnB,KAAK,aACH,OAAO,EAAE,MAAM,GAAG;EACpB,KAAK,aACH,OAAO,EAAE,MAAM,EAAc;EAC/B,KAAK,WACH,OAAO,EAAE,MAAM,GAAe;EAChC,KAAK,QAKH,OAAO,EAAE,MAAM,CAAC,KAAiB,EAAE;EACrC,KAAK,OACH,OAAO,EAAE,MAAM,IAAoB,EAAc;EACnD,KAAK,UACH,OAAO,EAAE,QAAQ,IAAW,MAAM,GAAG;EACvC,KAAK,YACH,OAAO,EAAE,QAAQ,IAAW,KAAK,EAAE;EACrC,SACE;CACJ;AACF;AAWA,SAAgB,EAAU,GAAiC;CACzD,QAAQ,GAAR;EACE,KAAK,cACH,OAAO;EACT,KAAK,aACH,OAAO;EACT,KAAK,aACH,OAAA;EACF,KAAK,WACH,OAAO;EACT,SACE;CACJ;AACF"}

package/dist/components/VDialog/VDialog.css

@@ -0,0 +1,2 @@
+@layer vectis.reset, vectis.tokens, vectis.components, vectis.utilities;
+@layer vectis.components{.v-dialog{inline-size:var(--dialog-width);max-inline-size:calc(100dvi - 2 * var(--vectis-space-4));max-block-size:calc(100dvb - 2 * var(--vectis-space-4));border-radius:var(--vectis-radius-overlay);background:var(--vectis-color-surface-overlay);color:var(--vectis-color-text);box-shadow:var(--vectis-shadow-xl);font-family:var(--vectis-text-family);border:none;flex-direction:column;margin:auto;padding:0;display:flex;overflow:hidden}.v-dialog:not([open]){display:none}.v-dialog:focus-visible{outline:none}.v-dialog-scroll{flex-direction:column;flex:auto;min-block-size:0;display:flex;overflow-y:auto;container-type:scroll-state}.v-dialog-edge{background:0 0;flex:none;block-size:1px;position:sticky}.v-dialog-edge--top{margin-block-end:-1px;inset-block-start:0}.v-dialog-edge--bottom{margin-block-start:-1px;inset-block-end:0}.v-dialog-header{justify-content:space-between;align-items:flex-start;gap:var(--vectis-space-4);padding:var(--vectis-space-6) var(--vectis-space-6) var(--vectis-space-3);flex:none;display:flex}.v-dialog-titles{flex-direction:column;min-inline-size:0;display:flex}.v-dialog-header-actions{align-items:center;gap:var(--vectis-space-1);margin-block-start:calc(-1 * var(--vectis-space-1));margin-inline-end:calc(-1 * var(--vectis-space-2));display:flex}.v-dialog-body{padding:var(--vectis-space-1) var(--vectis-space-6) var(--vectis-space-3);color:var(--vectis-color-text);font-size:var(--vectis-text-body-md-size);line-height:var(--vectis-text-body-md-leading);flex:1 0 auto}.v-dialog-footer{justify-content:flex-end;align-items:center;gap:var(--vectis-space-3);padding:var(--vectis-space-3) var(--vectis-space-6) var(--vectis-space-6);flex-wrap:wrap;flex:none;display:flex}@container scroll-state(scrollable:top){.v-dialog-edge--top{background:var(--vectis-color-border)}}@container scroll-state(scrollable:bottom){.v-dialog-edge--bottom{background:var(--vectis-color-border)}}.v-dialog{transition:opacity var(--vectis-duration-base) var(--vectis-ease-default), transform var(--vectis-duration-base) var(--vectis-ease-default)}@starting-style{.v-dialog[open]{opacity:0;transform:scale(.97)}}.v-dialog::backdrop{background:var(--vectis-color-backdrop);transition:opacity var(--vectis-duration-base) var(--vectis-ease-default)}@starting-style{.v-dialog[open]::backdrop{opacity:0}}@media (prefers-reduced-motion:reduce){.v-dialog,.v-dialog::backdrop{transition:none}}}

package/dist/components/VDialog/VDialog.d.ts

@@ -0,0 +1,96 @@
+/**
+ * A modal dialog: it takes over the page until the reader answers it.
+ *
+ * Almost everything that makes a modal correct comes free with the native `<dialog>`
+ * element opened as a modal — it is drawn above the whole page, the background is
+ * dimmed and made unusable, the focus is trapped inside it and handed back to the
+ * trigger on closing, and whether a click outside or Escape dismisses it is declared
+ * with an attribute rather than coded.
+ *
+ * The ONLY behavioural JavaScript is the bridge between `v-model:open` and the two
+ * methods the platform offers no declarative equivalent for: opening as a modal, and
+ * closing.
+ */
+interface DialogProps {
+    /**
+     * The title of the dialog, which also names it for assistive technology. It is
+     * ignored when the `#header` slot replaces the whole header.
+     */
+    title?: string;
+    /** A line under the title, explaining what the dialog is asking. */
+    subtitle?: string;
+    /**
+     * How wide the dialog is, in any CSS unit. It is never allowed to exceed the width
+     * of the viewport.
+     */
+    width?: string;
+    /**
+     * What kind of dialog this is. `alertdialog` is for one that must be answered
+     * explicitly, and it makes screen readers announce it more insistently — see
+     * VDialogAlert, which is exactly that.
+     */
+    role?: 'dialog' | 'alertdialog';
+    /** Shows the close cross in the header. */
+    closable?: boolean;
+    /** Lets a click outside the dialog close it. */
+    closeOnBackdrop?: boolean;
+    /** Lets the Escape key close the dialog. */
+    closeOnEscape?: boolean;
+    /** What the close cross does, in words. It falls back to the design system dictionary. */
+    closeLabel?: string;
+}
+type __VLS_Props = DialogProps;
+/** What the trigger has to carry: the click that opens the dialog, and the fact that it does. */
+type TriggerProps = {
+    onClick: () => void;
+    'aria-haspopup': 'dialog';
+};
+type __VLS_Slots = {
+    /** The body of the dialog. This is the part that scrolls when there is too much of it. */
+    default(): unknown;
+    /** Replaces the title and subtitle block with content of your own. */
+    header?(): unknown;
+    /** Extra controls in the header, placed before the close cross — a menu, a full-screen toggle. */
+    headerActions?(): unknown;
+    /** The buttons at the foot of the dialog. */
+    footer?(): unknown;
+    /**
+     * The button that opens the dialog. Bind the `triggerProps` it receives onto it. It
+     * stays rendered at all times, unlike the dialog itself.
+     */
+    trigger?(props: {
+        triggerProps: TriggerProps;
+    }): unknown;
+};
+declare function show(): void;
+declare function requestClose(): void;
+type __VLS_ModelProps = {
+    'open'?: boolean;
+};
+type __VLS_PublicProps = __VLS_Props & __VLS_ModelProps;
+declare const __VLS_base: import('vue').DefineComponent<__VLS_PublicProps, {
+    show: typeof show;
+    close: typeof requestClose;
+    el: import('vue').Ref<HTMLDialogElement | null, HTMLDialogElement | null>;
+}, {}, {}, {}, import('vue').ComponentOptionsMixin, import('vue').ComponentOptionsMixin, {
+    "update:open": (value: boolean) => any;
+}, string, import('vue').PublicProps, Readonly<__VLS_PublicProps> & Readonly<{
+    "onUpdate:open"?: ((value: boolean) => any) | undefined;
+}>, {
+    title: string;
+    role: "dialog" | "alertdialog";
+    subtitle: string;
+    width: string;
+    closable: boolean;
+    closeLabel: string;
+    closeOnBackdrop: boolean;
+    closeOnEscape: boolean;
+}, {}, {}, {}, string, import('vue').ComponentProvideOptions, false, {}, any>;
+declare const __VLS_export: __VLS_WithSlots<typeof __VLS_base, __VLS_Slots>;
+declare const _default: typeof __VLS_export;
+export default _default;
+type __VLS_WithSlots<T, S> = T & {
+    new (): {
+        $slots: S;
+    };
+};

package/dist/components/VDialog/VDialog.js

@@ -0,0 +1,9 @@
+import './VDialog.css';
+import e from "./VDialog.vue_vue_type_script_setup_true_lang.js";
+/* empty css                                        */
+//#region src/components/VDialog/VDialog.vue
+var t = e;
+//#endregion
+export { t as default };
+
+//# sourceMappingURL=VDialog.js.map

package/dist/components/VDialog/VDialog.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"VDialog.js","names":[],"sources":["../../../src/components/VDialog/VDialog.vue"],"sourcesContent":["<script setup lang=\"ts\">\nimport { computed, nextTick, onMounted, ref, useAttrs, useId, watch } from 'vue'\n\nimport VIcon from '../VIcon/VIcon.vue'\nimport { close as closeIcon } from '../VIcon/icons/close'\nimport VIconButton from '../VIconButton/VIconButton.vue'\nimport VTypography from '../VTypography/VTypography.vue'\nimport { useMessages } from '../../i18n/state'\n\n// @core\n/**\n * A modal dialog: it takes over the page until the reader answers it.\n *\n * Almost everything that makes a modal correct comes free with the native `<dialog>`\n * element opened as a modal — it is drawn above the whole page, the background is\n * dimmed and made unusable, the focus is trapped inside it and handed back to the\n * trigger on closing, and whether a click outside or Escape dismisses it is declared\n * with an attribute rather than coded.\n *\n * The ONLY behavioural JavaScript is the bridge between `v-model:open` and the two\n * methods the platform offers no declarative equivalent for: opening as a modal, and\n * closing.\n */\ninterface DialogProps {\n  /**\n   * The title of the dialog, which also names it for assistive technology. It is\n   * ignored when the `#header` slot replaces the whole header.\n   */\n  title?: string\n  /** A line under the title, explaining what the dialog is asking. */\n  subtitle?: string\n  /**\n   * How wide the dialog is, in any CSS unit. It is never allowed to exceed the width\n   * of the viewport.\n   */\n  width?: string\n  /**\n   * What kind of dialog this is. `alertdialog` is for one that must be answered\n   * explicitly, and it makes screen readers announce it more insistently — see\n   * VDialogAlert, which is exactly that.\n   */\n  role?: 'dialog' | 'alertdialog'\n  /** Shows the close cross in the header. */\n  closable?: boolean\n  /** Lets a click outside the dialog close it. */\n  closeOnBackdrop?: boolean\n  /** Lets the Escape key close the dialog. */\n  closeOnEscape?: boolean\n  /** What the close cross does, in words. It falls back to the design system dictionary. */\n  closeLabel?: string\n}\n\nconst props = withDefaults(defineProps<DialogProps>(), {\n  title: undefined,\n  subtitle: undefined,\n  width: '400px',\n  role: 'dialog',\n  closable: true,\n  closeOnBackdrop: true,\n  closeOnEscape: true,\n  closeLabel: undefined,\n})\n\nconst m = useMessages()\nconst resolvedCloseLabel = computed(() => props.closeLabel ?? m.value.common.close)\n\nconst open = defineModel<boolean>('open', { default: false })\n\n/** What the trigger has to carry: the click that opens the dialog, and the fact that it does. */\ntype TriggerProps = {\n  onClick: () => void\n  'aria-haspopup': 'dialog'\n}\n\ndefineSlots<{\n  /** The body of the dialog. This is the part that scrolls when there is too much of it. */\n  default(): unknown\n  /** Replaces the title and subtitle block with content of your own. */\n  header?(): unknown\n  /** Extra controls in the header, placed before the close cross — a menu, a full-screen toggle. */\n  headerActions?(): unknown\n  /** The buttons at the foot of the dialog. */\n  footer?(): unknown\n  /**\n   * The button that opens the dialog. Bind the `triggerProps` it receives onto it. It\n   * stays rendered at all times, unlike the dialog itself.\n   */\n  trigger?(props: { triggerProps: TriggerProps }): unknown\n}>()\n\ndefineOptions({ inheritAttrs: false })\n\nconst attrs = useAttrs()\nconst dialogEl = ref<HTMLDialogElement | null>(null)\nconst titleId = useId()\nconst subtitleId = useId()\n\n/**\n * Which dismissals the browser itself accepts, declared as an attribute rather than\n * handled in code: everything, Escape alone, or nothing.\n *\n * One combination cannot be expressed that way — a click outside allowed while Escape\n * is not — and it falls back to allowing both. Nothing in the design system asks for\n * it, and it would be a strange thing to want.\n */\nconst closedby = computed(() =>\n  props.closeOnBackdrop ? 'any' : props.closeOnEscape ? 'closerequest' : 'none',\n)\n\n// @fallback\n// The `closedby` attribute is newer than the type definitions shipped with\n// TypeScript, so writing it directly in the template would be reported as an unknown\n// attribute. Passing it inside a bound object goes through the same path as any\n// forwarded attribute, which is not checked element by element. Vue still merges the\n// `class` and `style` it may contain with the static ones below.\nconst rootAttrs = computed(() => ({ ...attrs, closedby: closedby.value }))\n\n// The dialog and its content only exist while it is open, which also spares the page\n// whatever heavy thing it contains. Every opening therefore builds a BRAND NEW\n// element, so it is always opened as a modal from a clean slate, and closing removes\n// it entirely — nothing is left behind to swallow clicks, and reopening cannot race\n// with a closing that is still finishing. The trigger, by contrast, stays rendered at\n// all times.\nconst rendered = ref(open.value)\n\nfunction show() {\n  open.value = true\n}\n\nfunction requestClose() {\n  // Closing the element is enough: the browser then fires its own close event, which\n  // is what puts the model back in step below.\n  dialogEl.value?.close()\n}\n\nconst triggerProps = computed<TriggerProps>(() => ({\n  onClick: show,\n  'aria-haspopup': 'dialog',\n}))\n\n// The `<dialog>` element is asymmetric in a way that shapes this whole bridge: it\n// announces every closing with an event, but announces nothing at all when it opens —\n// where a popover reports both. So the two directions are not written the same way:\n//\n//  - opening: render the element, then, once Vue has actually put it in the document,\n//    open it as a modal;\n//  - closing: whatever closed it — the cross, our own call, Escape, a click outside —\n//    the browser's close event is what puts the model back in step, and only then is\n//    the element removed.\nwatch(open, async (value) => {\n  if (value) {\n    rendered.value = true\n    await nextTick() // the brand new <dialog> has to exist before it can be opened\n    dialogEl.value?.showModal()\n  } else {\n    dialogEl.value?.close()\n    rendered.value = false\n  }\n})\n\n// @ssr\nonMounted(() => {\n  // A watcher does not run during the server render, so a dialog asked to be open from\n  // the start would never be opened. The element is already there — the flag above was\n  // initialized from the model — it just has to be told to show itself.\n  if (open.value) dialogEl.value?.showModal()\n})\n\n// The browser's own close event, whatever caused it, is what brings the model back in\n// step with reality.\nfunction onClose() {\n  open.value = false\n}\n\ndefineExpose({ show, close: requestClose, el: dialogEl })\n</script>\n\n<template>\n  <slot name=\"trigger\" :trigger-props=\"triggerProps\" />\n  <dialog\n    v-if=\"rendered\"\n    ref=\"dialogEl\"\n    v-bind=\"rootAttrs\"\n    class=\"v-dialog\"\n    :style=\"{ '--dialog-width': width }\"\n    :role=\"role === 'alertdialog' ? 'alertdialog' : undefined\"\n    :aria-labelledby=\"title ? titleId : undefined\"\n    :aria-describedby=\"subtitle ? subtitleId : undefined\"\n    @close=\"onClose\"\n  >\n    <!--\n      The header and the footer stay put while only the body scrolls, so the scrollbar\n      is confined to the body and never runs along them.\n\n      The lines that appear under the header and above the footer once the body is\n      scrolled are drawn by two sentinels stuck INSIDE the scrolling area, and not by\n      the header and footer themselves: a container query can only style what is inside\n      the container it asks about, never a sibling of it.\n    -->\n    <header class=\"v-dialog-header\">\n      <slot name=\"header\">\n        <div class=\"v-dialog-titles\">\n          <VTypography\n            v-if=\"title\"\n            :id=\"titleId\"\n            as=\"h2\"\n            variant=\"heading-3\"\n            class=\"v-dialog-title\"\n          >\n            {{ title }}\n          </VTypography>\n          <VTypography\n            v-if=\"subtitle\"\n            :id=\"subtitleId\"\n            variant=\"subtitle\"\n            tone=\"muted\"\n            class=\"v-dialog-subtitle\"\n          >\n            {{ subtitle }}\n          </VTypography>\n        </div>\n      </slot>\n      <div v-if=\"closable || $slots.headerActions\" class=\"v-dialog-header-actions\">\n        <slot name=\"headerActions\" />\n        <VIconButton\n          v-if=\"closable\"\n          class=\"v-dialog-close\"\n          :label=\"resolvedCloseLabel\"\n          variant=\"ghost\"\n          tone=\"neutral\"\n          size=\"sm\"\n          @click=\"requestClose\"\n        >\n          <VIcon :name=\"closeIcon\" />\n        </VIconButton>\n      </div>\n    </header>\n    <div class=\"v-dialog-scroll\">\n      <span class=\"v-dialog-edge v-dialog-edge--top\" aria-hidden=\"true\" />\n      <div class=\"v-dialog-body\">\n        <slot />\n      </div>\n      <span class=\"v-dialog-edge v-dialog-edge--bottom\" aria-hidden=\"true\" />\n    </div>\n    <footer v-if=\"$slots.footer\" class=\"v-dialog-footer\">\n      <slot name=\"footer\" />\n    </footer>\n  </dialog>\n</template>\n\n<style>\n@layer vectis.components {\n  .v-dialog {\n    /* The width comes from the prop, set inline. Whatever it asks for, the dialog is\n       never allowed past the viewport, margins included. */\n    inline-size: var(--dialog-width);\n    max-inline-size: calc(100dvi - 2 * var(--vectis-space-4));\n    max-block-size: calc(100dvb - 2 * var(--vectis-space-4));\n    /* This puts the dialog back in the middle of the screen. The browser centres a\n       modal with an automatic margin, which the design system's own reset — where\n       every element loses its margins — had removed; restoring it here works because\n       the component layer is stronger than the reset one. */\n    margin: auto;\n    /* The header and footer stay put while only the body scrolls, and hiding the\n       overflow is what keeps the content inside the rounded corners. */\n    display: flex;\n    flex-direction: column;\n    overflow: hidden;\n    padding: 0;\n    border: none;\n    border-radius: var(--vectis-radius-overlay);\n    background: var(--vectis-color-surface-overlay);\n    color: var(--vectis-color-text);\n    box-shadow: var(--vectis-shadow-xl);\n    font-family: var(--vectis-text-family);\n  }\n\n  /*\n   * An indispensable guard. The browser hides a closed dialog with a rule of its own,\n   * but any display we declare above beats it — so without this, a closed dialog would\n   * sit in the page at the top left, swallowing clicks.\n   *\n   * It also covers the two moments where the element exists without being open yet: the\n   * frame between rendering it and opening it, and the server-rendered markup. The\n   * popovers have the very same guard.\n   */\n  .v-dialog:not([open]) {\n    display: none;\n  }\n\n  /* Opening a modal puts the focus on the dialog itself. No ring is drawn around the\n     whole thing for that: the focus a reader needs to see is the one on the controls\n     inside. */\n  .v-dialog:focus-visible {\n    outline: none;\n  }\n\n  .v-dialog-scroll {\n    /* The ONLY part that scrolls. It takes whatever room is left between the header\n       and the footer, which is what keeps the scrollbar confined to it. The zero\n       minimum is load-bearing: without it a flex item refuses to shrink below its\n       content, and nothing would ever scroll. */\n    flex: 1 1 auto;\n    min-block-size: 0;\n    overflow-y: auto;\n    display: flex;\n    flex-direction: column;\n    /* This makes the box something its descendants can ask questions about — namely\n       whether there is content hidden above or below. It adds no containment of size. */\n    container-type: scroll-state;\n  }\n\n  /*\n   * The two sentinels: hairlines stuck to the top and the bottom of the scrolling\n   * area, and descendants of it, which is what allows them to ask about its scroll\n   * state. Their negative margins mean they occupy no space at all. They are\n   * transparent until the rules further down reveal them.\n   */\n  .v-dialog-edge {\n    flex: none;\n    block-size: 1px;\n    position: sticky;\n    background: transparent;\n  }\n\n  .v-dialog-edge--top {\n    inset-block-start: 0;\n    margin-block-end: -1px;\n  }\n\n  .v-dialog-edge--bottom {\n    inset-block-end: 0;\n    margin-block-start: -1px;\n  }\n\n  .v-dialog-header {\n    flex: none; /* stays at the top, outside whatever scrolls */\n    display: flex;\n    align-items: flex-start;\n    justify-content: space-between;\n    gap: var(--vectis-space-4);\n    padding: var(--vectis-space-6) var(--vectis-space-6) var(--vectis-space-3);\n  }\n\n  .v-dialog-titles {\n    display: flex;\n    flex-direction: column;\n    min-inline-size: 0;\n  }\n\n  /* The title and the subtitle are rendered by VTypography, which carries their type.\n     Their classes remain as hooks, for a consumer's overrides and for the tests. */\n\n  .v-dialog-header-actions {\n    display: flex;\n    align-items: center;\n    gap: var(--vectis-space-1);\n    /* The cross is a button, so it carries invisible padding of its own; pulling the\n       row back by that amount is what makes the glyph line up with the header's edge\n       rather than floating inside it. */\n    margin-block-start: calc(-1 * var(--vectis-space-1));\n    margin-inline-end: calc(-1 * var(--vectis-space-2));\n  }\n\n  .v-dialog-body {\n    /* Short content is stretched to fill the space, so the footer stays at the bottom\n       of the dialog rather than floating halfway up; long content keeps its natural\n       height, overflows, and is what scrolls. */\n    flex: 1 0 auto;\n    padding: var(--vectis-space-1) var(--vectis-space-6) var(--vectis-space-3);\n    color: var(--vectis-color-text);\n    font-size: var(--vectis-text-body-md-size);\n    line-height: var(--vectis-text-body-md-leading);\n  }\n\n  .v-dialog-footer {\n    flex: none; /* stays at the bottom, outside whatever scrolls */\n    display: flex;\n    align-items: center;\n    justify-content: flex-end;\n    flex-wrap: wrap;\n    gap: var(--vectis-space-3);\n    padding: var(--vectis-space-3) var(--vectis-space-6) var(--vectis-space-6);\n  }\n\n  /*\n   * The lines only appear when they mean something. Asking the scrolling area whether\n   * it can still be scrolled upwards tells us content is hidden ABOVE, so the line\n   * under the header is shown; the same question downwards reveals the one above the\n   * footer. In other words each line is drawn exactly when content is passing behind\n   * the edge it marks.\n   *\n   * This kind of query is Chrome 133 and later for now. Where it is missing the\n   * sentinels simply stay transparent, which is the intended fallback.\n   */\n  @container scroll-state(scrollable: top) {\n    .v-dialog-edge--top {\n      background: var(--vectis-color-border);\n    }\n  }\n\n  @container scroll-state(scrollable: bottom) {\n    .v-dialog-edge--bottom {\n      background: var(--vectis-color-border);\n    }\n  }\n\n  /*\n   * The dialog animates on the way IN and not on the way out. Since it is removed from\n   * the page the moment it closes, there is nothing left to animate out — that is the\n   * price of the clean slate the lazy rendering buys, and it also spares the extra\n   * declarations an exit animation would need.\n   *\n   * The starting values below are where a freshly rendered dialog begins, before\n   * settling into its open state.\n   */\n  .v-dialog {\n    transition:\n      opacity var(--vectis-duration-base) var(--vectis-ease-default),\n      transform var(--vectis-duration-base) var(--vectis-ease-default);\n  }\n\n  @starting-style {\n    .v-dialog[open] {\n      opacity: 0;\n      transform: scale(0.97);\n    }\n  }\n\n  .v-dialog::backdrop {\n    background: var(--vectis-color-backdrop);\n    transition: opacity var(--vectis-duration-base) var(--vectis-ease-default);\n  }\n\n  @starting-style {\n    .v-dialog[open]::backdrop {\n      opacity: 0;\n    }\n  }\n\n  @media (prefers-reduced-motion: reduce) {\n    .v-dialog,\n    .v-dialog::backdrop {\n      transition: none;\n    }\n  }\n}\n</style>\n"],"mappings":""}

package/dist/components/VDialog/VDialog.vue_vue_type_script_setup_true_lang.js

@@ -0,0 +1,134 @@
+import { useMessages as e } from "../../i18n/state.js";
+import t from "../VIcon/VIcon.js";
+import n from "../VTypography/VTypography.js";
+import r from "../VIconButton/VIconButton.js";
+import { close as i } from "../VIcon/icons/close.js";
+import { Fragment as a, computed as o, createBlock as s, createCommentVNode as c, createElementBlock as l, createElementVNode as u, createTextVNode as d, createVNode as f, defineComponent as p, mergeModels as m, mergeProps as h, nextTick as g, onMounted as _, openBlock as v, ref as y, renderSlot as b, toDisplayString as x, unref as S, useAttrs as C, useId as w, useModel as T, watch as E, withCtx as D } from "vue";
+//#region src/components/VDialog/VDialog.vue?vue&type=script&setup=true&lang.ts
+var O = [
+	"role",
+	"aria-labelledby",
+	"aria-describedby"
+], k = { class: "v-dialog-header" }, A = { class: "v-dialog-titles" }, j = {
+	key: 0,
+	class: "v-dialog-header-actions"
+}, M = { class: "v-dialog-scroll" }, N = { class: "v-dialog-body" }, P = {
+	key: 0,
+	class: "v-dialog-footer"
+}, F = /*@__PURE__*/ p({
+	inheritAttrs: !1,
+	__name: "VDialog",
+	props: /*@__PURE__*/ m({
+		title: { default: void 0 },
+		subtitle: { default: void 0 },
+		width: { default: "400px" },
+		role: { default: "dialog" },
+		closable: {
+			type: Boolean,
+			default: !0
+		},
+		closeOnBackdrop: {
+			type: Boolean,
+			default: !0
+		},
+		closeOnEscape: {
+			type: Boolean,
+			default: !0
+		},
+		closeLabel: { default: void 0 }
+	}, {
+		open: {
+			type: Boolean,
+			default: !1
+		},
+		openModifiers: {}
+	}),
+	emits: ["update:open"],
+	setup(p, { expose: m }) {
+		let F = p, I = e(), L = o(() => F.closeLabel ?? I.value.common.close), R = T(p, "open"), z = C(), B = y(null), V = w(), H = w(), U = o(() => F.closeOnBackdrop ? "any" : F.closeOnEscape ? "closerequest" : "none"), W = o(() => ({
+			...z,
+			closedby: U.value
+		})), G = y(R.value);
+		function K() {
+			R.value = !0;
+		}
+		function q() {
+			B.value?.close();
+		}
+		let J = o(() => ({
+			onClick: K,
+			"aria-haspopup": "dialog"
+		}));
+		E(R, async (e) => {
+			e ? (G.value = !0, await g(), B.value?.showModal()) : (B.value?.close(), G.value = !1);
+		}), _(() => {
+			R.value && B.value?.showModal();
+		});
+		function Y() {
+			R.value = !1;
+		}
+		return m({
+			show: K,
+			close: q,
+			el: B
+		}), (e, o) => (v(), l(a, null, [b(e.$slots, "trigger", { triggerProps: J.value }), G.value ? (v(), l("dialog", h({
+			key: 0,
+			ref_key: "dialogEl",
+			ref: B
+		}, W.value, {
+			class: "v-dialog",
+			style: { "--dialog-width": p.width },
+			role: p.role === "alertdialog" ? "alertdialog" : void 0,
+			"aria-labelledby": p.title ? S(V) : void 0,
+			"aria-describedby": p.subtitle ? S(H) : void 0,
+			onClose: Y
+		}), [
+			u("header", k, [b(e.$slots, "header", {}, () => [u("div", A, [p.title ? (v(), s(n, {
+				key: 0,
+				id: S(V),
+				as: "h2",
+				variant: "heading-3",
+				class: "v-dialog-title"
+			}, {
+				default: D(() => [d(x(p.title), 1)]),
+				_: 1
+			}, 8, ["id"])) : c("", !0), p.subtitle ? (v(), s(n, {
+				key: 1,
+				id: S(H),
+				variant: "subtitle",
+				tone: "muted",
+				class: "v-dialog-subtitle"
+			}, {
+				default: D(() => [d(x(p.subtitle), 1)]),
+				_: 1
+			}, 8, ["id"])) : c("", !0)])]), p.closable || e.$slots.headerActions ? (v(), l("div", j, [b(e.$slots, "headerActions"), p.closable ? (v(), s(r, {
+				key: 0,
+				class: "v-dialog-close",
+				label: L.value,
+				variant: "ghost",
+				tone: "neutral",
+				size: "sm",
+				onClick: q
+			}, {
+				default: D(() => [f(t, { name: S(i) }, null, 8, ["name"])]),
+				_: 1
+			}, 8, ["label"])) : c("", !0)])) : c("", !0)]),
+			u("div", M, [
+				o[0] ||= u("span", {
+					class: "v-dialog-edge v-dialog-edge--top",
+					"aria-hidden": "true"
+				}, null, -1),
+				u("div", N, [b(e.$slots, "default")]),
+				o[1] ||= u("span", {
+					class: "v-dialog-edge v-dialog-edge--bottom",
+					"aria-hidden": "true"
+				}, null, -1)
+			]),
+			e.$slots.footer ? (v(), l("footer", P, [b(e.$slots, "footer")])) : c("", !0)
+		], 16, O)) : c("", !0)], 64));
+	}
+});
+//#endregion
+export { F as default };
+
+//# sourceMappingURL=VDialog.vue_vue_type_script_setup_true_lang.js.map

package/dist/components/VDialog/VDialog.vue_vue_type_script_setup_true_lang.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"VDialog.vue_vue_type_script_setup_true_lang.js","names":["$slots"],"sources":["../../../src/components/VDialog/VDialog.vue"],"sourcesContent":["<script setup lang=\"ts\">\nimport { computed, nextTick, onMounted, ref, useAttrs, useId, watch } from 'vue'\n\nimport VIcon from '../VIcon/VIcon.vue'\nimport { close as closeIcon } from '../VIcon/icons/close'\nimport VIconButton from '../VIconButton/VIconButton.vue'\nimport VTypography from '../VTypography/VTypography.vue'\nimport { useMessages } from '../../i18n/state'\n\n// @core\n/**\n * A modal dialog: it takes over the page until the reader answers it.\n *\n * Almost everything that makes a modal correct comes free with the native `<dialog>`\n * element opened as a modal — it is drawn above the whole page, the background is\n * dimmed and made unusable, the focus is trapped inside it and handed back to the\n * trigger on closing, and whether a click outside or Escape dismisses it is declared\n * with an attribute rather than coded.\n *\n * The ONLY behavioural JavaScript is the bridge between `v-model:open` and the two\n * methods the platform offers no declarative equivalent for: opening as a modal, and\n * closing.\n */\ninterface DialogProps {\n  /**\n   * The title of the dialog, which also names it for assistive technology. It is\n   * ignored when the `#header` slot replaces the whole header.\n   */\n  title?: string\n  /** A line under the title, explaining what the dialog is asking. */\n  subtitle?: string\n  /**\n   * How wide the dialog is, in any CSS unit. It is never allowed to exceed the width\n   * of the viewport.\n   */\n  width?: string\n  /**\n   * What kind of dialog this is. `alertdialog` is for one that must be answered\n   * explicitly, and it makes screen readers announce it more insistently — see\n   * VDialogAlert, which is exactly that.\n   */\n  role?: 'dialog' | 'alertdialog'\n  /** Shows the close cross in the header. */\n  closable?: boolean\n  /** Lets a click outside the dialog close it. */\n  closeOnBackdrop?: boolean\n  /** Lets the Escape key close the dialog. */\n  closeOnEscape?: boolean\n  /** What the close cross does, in words. It falls back to the design system dictionary. */\n  closeLabel?: string\n}\n\nconst props = withDefaults(defineProps<DialogProps>(), {\n  title: undefined,\n  subtitle: undefined,\n  width: '400px',\n  role: 'dialog',\n  closable: true,\n  closeOnBackdrop: true,\n  closeOnEscape: true,\n  closeLabel: undefined,\n})\n\nconst m = useMessages()\nconst resolvedCloseLabel = computed(() => props.closeLabel ?? m.value.common.close)\n\nconst open = defineModel<boolean>('open', { default: false })\n\n/** What the trigger has to carry: the click that opens the dialog, and the fact that it does. */\ntype TriggerProps = {\n  onClick: () => void\n  'aria-haspopup': 'dialog'\n}\n\ndefineSlots<{\n  /** The body of the dialog. This is the part that scrolls when there is too much of it. */\n  default(): unknown\n  /** Replaces the title and subtitle block with content of your own. */\n  header?(): unknown\n  /** Extra controls in the header, placed before the close cross — a menu, a full-screen toggle. */\n  headerActions?(): unknown\n  /** The buttons at the foot of the dialog. */\n  footer?(): unknown\n  /**\n   * The button that opens the dialog. Bind the `triggerProps` it receives onto it. It\n   * stays rendered at all times, unlike the dialog itself.\n   */\n  trigger?(props: { triggerProps: TriggerProps }): unknown\n}>()\n\ndefineOptions({ inheritAttrs: false })\n\nconst attrs = useAttrs()\nconst dialogEl = ref<HTMLDialogElement | null>(null)\nconst titleId = useId()\nconst subtitleId = useId()\n\n/**\n * Which dismissals the browser itself accepts, declared as an attribute rather than\n * handled in code: everything, Escape alone, or nothing.\n *\n * One combination cannot be expressed that way — a click outside allowed while Escape\n * is not — and it falls back to allowing both. Nothing in the design system asks for\n * it, and it would be a strange thing to want.\n */\nconst closedby = computed(() =>\n  props.closeOnBackdrop ? 'any' : props.closeOnEscape ? 'closerequest' : 'none',\n)\n\n// @fallback\n// The `closedby` attribute is newer than the type definitions shipped with\n// TypeScript, so writing it directly in the template would be reported as an unknown\n// attribute. Passing it inside a bound object goes through the same path as any\n// forwarded attribute, which is not checked element by element. Vue still merges the\n// `class` and `style` it may contain with the static ones below.\nconst rootAttrs = computed(() => ({ ...attrs, closedby: closedby.value }))\n\n// The dialog and its content only exist while it is open, which also spares the page\n// whatever heavy thing it contains. Every opening therefore builds a BRAND NEW\n// element, so it is always opened as a modal from a clean slate, and closing removes\n// it entirely — nothing is left behind to swallow clicks, and reopening cannot race\n// with a closing that is still finishing. The trigger, by contrast, stays rendered at\n// all times.\nconst rendered = ref(open.value)\n\nfunction show() {\n  open.value = true\n}\n\nfunction requestClose() {\n  // Closing the element is enough: the browser then fires its own close event, which\n  // is what puts the model back in step below.\n  dialogEl.value?.close()\n}\n\nconst triggerProps = computed<TriggerProps>(() => ({\n  onClick: show,\n  'aria-haspopup': 'dialog',\n}))\n\n// The `<dialog>` element is asymmetric in a way that shapes this whole bridge: it\n// announces every closing with an event, but announces nothing at all when it opens —\n// where a popover reports both. So the two directions are not written the same way:\n//\n//  - opening: render the element, then, once Vue has actually put it in the document,\n//    open it as a modal;\n//  - closing: whatever closed it — the cross, our own call, Escape, a click outside —\n//    the browser's close event is what puts the model back in step, and only then is\n//    the element removed.\nwatch(open, async (value) => {\n  if (value) {\n    rendered.value = true\n    await nextTick() // the brand new <dialog> has to exist before it can be opened\n    dialogEl.value?.showModal()\n  } else {\n    dialogEl.value?.close()\n    rendered.value = false\n  }\n})\n\n// @ssr\nonMounted(() => {\n  // A watcher does not run during the server render, so a dialog asked to be open from\n  // the start would never be opened. The element is already there — the flag above was\n  // initialized from the model — it just has to be told to show itself.\n  if (open.value) dialogEl.value?.showModal()\n})\n\n// The browser's own close event, whatever caused it, is what brings the model back in\n// step with reality.\nfunction onClose() {\n  open.value = false\n}\n\ndefineExpose({ show, close: requestClose, el: dialogEl })\n</script>\n\n<template>\n  <slot name=\"trigger\" :trigger-props=\"triggerProps\" />\n  <dialog\n    v-if=\"rendered\"\n    ref=\"dialogEl\"\n    v-bind=\"rootAttrs\"\n    class=\"v-dialog\"\n    :style=\"{ '--dialog-width': width }\"\n    :role=\"role === 'alertdialog' ? 'alertdialog' : undefined\"\n    :aria-labelledby=\"title ? titleId : undefined\"\n    :aria-describedby=\"subtitle ? subtitleId : undefined\"\n    @close=\"onClose\"\n  >\n    <!--\n      The header and the footer stay put while only the body scrolls, so the scrollbar\n      is confined to the body and never runs along them.\n\n      The lines that appear under the header and above the footer once the body is\n      scrolled are drawn by two sentinels stuck INSIDE the scrolling area, and not by\n      the header and footer themselves: a container query can only style what is inside\n      the container it asks about, never a sibling of it.\n    -->\n    <header class=\"v-dialog-header\">\n      <slot name=\"header\">\n        <div class=\"v-dialog-titles\">\n          <VTypography\n            v-if=\"title\"\n            :id=\"titleId\"\n            as=\"h2\"\n            variant=\"heading-3\"\n            class=\"v-dialog-title\"\n          >\n            {{ title }}\n          </VTypography>\n          <VTypography\n            v-if=\"subtitle\"\n            :id=\"subtitleId\"\n            variant=\"subtitle\"\n            tone=\"muted\"\n            class=\"v-dialog-subtitle\"\n          >\n            {{ subtitle }}\n          </VTypography>\n        </div>\n      </slot>\n      <div v-if=\"closable || $slots.headerActions\" class=\"v-dialog-header-actions\">\n        <slot name=\"headerActions\" />\n        <VIconButton\n          v-if=\"closable\"\n          class=\"v-dialog-close\"\n          :label=\"resolvedCloseLabel\"\n          variant=\"ghost\"\n          tone=\"neutral\"\n          size=\"sm\"\n          @click=\"requestClose\"\n        >\n          <VIcon :name=\"closeIcon\" />\n        </VIconButton>\n      </div>\n    </header>\n    <div class=\"v-dialog-scroll\">\n      <span class=\"v-dialog-edge v-dialog-edge--top\" aria-hidden=\"true\" />\n      <div class=\"v-dialog-body\">\n        <slot />\n      </div>\n      <span class=\"v-dialog-edge v-dialog-edge--bottom\" aria-hidden=\"true\" />\n    </div>\n    <footer v-if=\"$slots.footer\" class=\"v-dialog-footer\">\n      <slot name=\"footer\" />\n    </footer>\n  </dialog>\n</template>\n\n<style>\n@layer vectis.components {\n  .v-dialog {\n    /* The width comes from the prop, set inline. Whatever it asks for, the dialog is\n       never allowed past the viewport, margins included. */\n    inline-size: var(--dialog-width);\n    max-inline-size: calc(100dvi - 2 * var(--vectis-space-4));\n    max-block-size: calc(100dvb - 2 * var(--vectis-space-4));\n    /* This puts the dialog back in the middle of the screen. The browser centres a\n       modal with an automatic margin, which the design system's own reset — where\n       every element loses its margins — had removed; restoring it here works because\n       the component layer is stronger than the reset one. */\n    margin: auto;\n    /* The header and footer stay put while only the body scrolls, and hiding the\n       overflow is what keeps the content inside the rounded corners. */\n    display: flex;\n    flex-direction: column;\n    overflow: hidden;\n    padding: 0;\n    border: none;\n    border-radius: var(--vectis-radius-overlay);\n    background: var(--vectis-color-surface-overlay);\n    color: var(--vectis-color-text);\n    box-shadow: var(--vectis-shadow-xl);\n    font-family: var(--vectis-text-family);\n  }\n\n  /*\n   * An indispensable guard. The browser hides a closed dialog with a rule of its own,\n   * but any display we declare above beats it — so without this, a closed dialog would\n   * sit in the page at the top left, swallowing clicks.\n   *\n   * It also covers the two moments where the element exists without being open yet: the\n   * frame between rendering it and opening it, and the server-rendered markup. The\n   * popovers have the very same guard.\n   */\n  .v-dialog:not([open]) {\n    display: none;\n  }\n\n  /* Opening a modal puts the focus on the dialog itself. No ring is drawn around the\n     whole thing for that: the focus a reader needs to see is the one on the controls\n     inside. */\n  .v-dialog:focus-visible {\n    outline: none;\n  }\n\n  .v-dialog-scroll {\n    /* The ONLY part that scrolls. It takes whatever room is left between the header\n       and the footer, which is what keeps the scrollbar confined to it. The zero\n       minimum is load-bearing: without it a flex item refuses to shrink below its\n       content, and nothing would ever scroll. */\n    flex: 1 1 auto;\n    min-block-size: 0;\n    overflow-y: auto;\n    display: flex;\n    flex-direction: column;\n    /* This makes the box something its descendants can ask questions about — namely\n       whether there is content hidden above or below. It adds no containment of size. */\n    container-type: scroll-state;\n  }\n\n  /*\n   * The two sentinels: hairlines stuck to the top and the bottom of the scrolling\n   * area, and descendants of it, which is what allows them to ask about its scroll\n   * state. Their negative margins mean they occupy no space at all. They are\n   * transparent until the rules further down reveal them.\n   */\n  .v-dialog-edge {\n    flex: none;\n    block-size: 1px;\n    position: sticky;\n    background: transparent;\n  }\n\n  .v-dialog-edge--top {\n    inset-block-start: 0;\n    margin-block-end: -1px;\n  }\n\n  .v-dialog-edge--bottom {\n    inset-block-end: 0;\n    margin-block-start: -1px;\n  }\n\n  .v-dialog-header {\n    flex: none; /* stays at the top, outside whatever scrolls */\n    display: flex;\n    align-items: flex-start;\n    justify-content: space-between;\n    gap: var(--vectis-space-4);\n    padding: var(--vectis-space-6) var(--vectis-space-6) var(--vectis-space-3);\n  }\n\n  .v-dialog-titles {\n    display: flex;\n    flex-direction: column;\n    min-inline-size: 0;\n  }\n\n  /* The title and the subtitle are rendered by VTypography, which carries their type.\n     Their classes remain as hooks, for a consumer's overrides and for the tests. */\n\n  .v-dialog-header-actions {\n    display: flex;\n    align-items: center;\n    gap: var(--vectis-space-1);\n    /* The cross is a button, so it carries invisible padding of its own; pulling the\n       row back by that amount is what makes the glyph line up with the header's edge\n       rather than floating inside it. */\n    margin-block-start: calc(-1 * var(--vectis-space-1));\n    margin-inline-end: calc(-1 * var(--vectis-space-2));\n  }\n\n  .v-dialog-body {\n    /* Short content is stretched to fill the space, so the footer stays at the bottom\n       of the dialog rather than floating halfway up; long content keeps its natural\n       height, overflows, and is what scrolls. */\n    flex: 1 0 auto;\n    padding: var(--vectis-space-1) var(--vectis-space-6) var(--vectis-space-3);\n    color: var(--vectis-color-text);\n    font-size: var(--vectis-text-body-md-size);\n    line-height: var(--vectis-text-body-md-leading);\n  }\n\n  .v-dialog-footer {\n    flex: none; /* stays at the bottom, outside whatever scrolls */\n    display: flex;\n    align-items: center;\n    justify-content: flex-end;\n    flex-wrap: wrap;\n    gap: var(--vectis-space-3);\n    padding: var(--vectis-space-3) var(--vectis-space-6) var(--vectis-space-6);\n  }\n\n  /*\n   * The lines only appear when they mean something. Asking the scrolling area whether\n   * it can still be scrolled upwards tells us content is hidden ABOVE, so the line\n   * under the header is shown; the same question downwards reveals the one above the\n   * footer. In other words each line is drawn exactly when content is passing behind\n   * the edge it marks.\n   *\n   * This kind of query is Chrome 133 and later for now. Where it is missing the\n   * sentinels simply stay transparent, which is the intended fallback.\n   */\n  @container scroll-state(scrollable: top) {\n    .v-dialog-edge--top {\n      background: var(--vectis-color-border);\n    }\n  }\n\n  @container scroll-state(scrollable: bottom) {\n    .v-dialog-edge--bottom {\n      background: var(--vectis-color-border);\n    }\n  }\n\n  /*\n   * The dialog animates on the way IN and not on the way out. Since it is removed from\n   * the page the moment it closes, there is nothing left to animate out — that is the\n   * price of the clean slate the lazy rendering buys, and it also spares the extra\n   * declarations an exit animation would need.\n   *\n   * The starting values below are where a freshly rendered dialog begins, before\n   * settling into its open state.\n   */\n  .v-dialog {\n    transition:\n      opacity var(--vectis-duration-base) var(--vectis-ease-default),\n      transform var(--vectis-duration-base) var(--vectis-ease-default);\n  }\n\n  @starting-style {\n    .v-dialog[open] {\n      opacity: 0;\n      transform: scale(0.97);\n    }\n  }\n\n  .v-dialog::backdrop {\n    background: var(--vectis-color-backdrop);\n    transition: opacity var(--vectis-duration-base) var(--vectis-ease-default);\n  }\n\n  @starting-style {\n    .v-dialog[open]::backdrop {\n      opacity: 0;\n    }\n  }\n\n  @media (prefers-reduced-motion: reduce) {\n    .v-dialog,\n    .v-dialog::backdrop {\n      transition: none;\n    }\n  }\n}\n</style>\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EAoDA,IAAM,IAAQ,GAWR,IAAI,EAAY,GAChB,IAAqB,QAAe,EAAM,cAAc,EAAE,MAAM,OAAO,KAAK,GAE5E,IAAO,EAAoB,GAAC,MAA0B,GA0BtD,IAAQ,EAAS,GACjB,IAAW,EAA8B,IAAI,GAC7C,IAAU,EAAM,GAChB,IAAa,EAAM,GAUnB,IAAW,QACf,EAAM,kBAAkB,QAAQ,EAAM,gBAAgB,iBAAiB,MACzE,GAQM,IAAY,SAAgB;GAAE,GAAG;GAAO,UAAU,EAAS;EAAM,EAAE,GAQnE,IAAW,EAAI,EAAK,KAAK;EAE/B,SAAS,IAAO;GACd,EAAK,QAAQ;EACf;EAEA,SAAS,IAAe;GAGtB,EAAS,OAAO,MAAM;EACxB;EAEA,IAAM,IAAe,SAA8B;GACjD,SAAS;GACT,iBAAiB;EACnB,EAAE;EAuBF,AAZA,EAAM,GAAM,OAAO,MAAU;GAC3B,AAAI,KACF,EAAS,QAAQ,IACjB,MAAM,EAAS,GACf,EAAS,OAAO,UAAU,MAE1B,EAAS,OAAO,MAAM,GACtB,EAAS,QAAQ;EAErB,CAAC,GAGD,QAAgB;GAId,AAAI,EAAK,SAAO,EAAS,OAAO,UAAU;EAC5C,CAAC;EAID,SAAS,IAAU;GACjB,EAAK,QAAQ;EACf;SAEA,EAAa;GAAE;GAAM,OAAO;GAAc,IAAI;EAAS,CAAC,+BAItD,EAAqD,EAAA,QAAA,WAAA,EAA/B,cAAe,EAAA,MAAY,CAAA,GAEzC,EAAA,SAAA,EAAA,GADR,EAoES,UApET,EAoES;;YAlEH;GAAJ,KAAI;KACI,EAAA,OAAS;GACjB,OAAM;GACL,OAAK,EAAA,kBAAsB,EAAA,MAAK;GAChC,MAAM,EAAA,SAAI,gBAAA,gBAAqC,KAAA;GAC/C,mBAAiB,EAAA,QAAQ,EAAA,CAAA,IAAU,KAAA;GACnC,oBAAkB,EAAA,WAAW,EAAA,CAAA,IAAa,KAAA;GACnC;;GAWR,EAqCS,UArCT,GAqCS,CApCP,EAqBO,EAAA,QAAA,UAAA,CAAA,SAAA,CApBL,EAmBM,OAnBN,GAmBM,CAjBI,EAAA,SAAA,EAAA,GADR,EAQc,GAAA;;IANX,IAAI,EAAA,CAAA;IACL,IAAG;IACH,SAAQ;IACR,OAAM;;qBAEK,CAAA,EAAA,EAAR,EAAA,KAAK,GAAA,CAAA,CAAA,CAAA;;+BAGF,EAAA,YAAA,EAAA,GADR,EAQc,GAAA;;IANX,IAAI,EAAA,CAAA;IACL,SAAQ;IACR,MAAK;IACL,OAAM;;qBAEQ,CAAA,EAAA,EAAX,EAAA,QAAQ,GAAA,CAAA,CAAA,CAAA;;mCAIN,EAAA,YAAYA,EAAAA,OAAO,iBAAA,EAAA,GAA9B,EAaM,OAbN,GAaM,CAZJ,EAA6B,EAAA,QAAA,eAAA,GAErB,EAAA,YAAA,EAAA,GADR,EAUc,GAAA;;IARZ,OAAM;IACL,OAAO,EAAA;IACR,SAAQ;IACR,MAAK;IACL,MAAK;IACJ,SAAO;;qBAEmB,CAA3B,EAA2B,GAAA,EAAnB,MAAM,EAAA,CAAA,EAAS,GAAA,MAAA,GAAA,CAAA,MAAA,CAAA,CAAA,CAAA;;;GAI7B,EAMM,OANN,GAMM;aALJ,EAAoE,QAAA;KAA9D,OAAM;KAAmC,eAAY;;IAC3D,EAEM,OAFN,GAEM,CADJ,EAAQ,EAAA,QAAA,SAAA,CAAA,CAAA;aAEV,EAAuE,QAAA;KAAjE,OAAM;KAAsC,eAAY;;;GAElDA,EAAAA,OAAO,UAAA,EAAA,GAArB,EAES,UAFT,GAES,CADP,EAAsB,EAAA,QAAA,QAAA,CAAA,CAAA,KAAA,EAAA,IAAA,EAAA"}

package/dist/components/VDialog/VDialogAlert.d.ts

@@ -0,0 +1,67 @@
+/**
+ * A dialog demanding an answer: confirming something irreversible, acknowledging a
+ * failure. It looks exactly like VDialog and is nothing more than VDialog with its
+ * options fixed, but those fixed options change what it is.
+ *
+ * It is announced to assistive technology as an alert rather than an ordinary dialog,
+ * and every casual way out is closed off: there is no cross, a click outside does
+ * nothing, and Escape does nothing either. The buttons in the footer are the only way
+ * to dismiss it — which is why supplying them is not optional.
+ */
+interface DialogAlertProps {
+    /**
+     * The question being asked, which also names the dialog for assistive technology.
+     * It is ignored when the `#header` slot replaces the whole header.
+     */
+    title?: string;
+    /** A line under the title, spelling out the consequences of the answer. */
+    subtitle?: string;
+    /**
+     * How wide the dialog is, in any CSS unit. It is never allowed to exceed the width
+     * of the viewport.
+     */
+    width?: string;
+}
+type __VLS_Props = DialogAlertProps;
+type TriggerProps = {
+    onClick: () => void;
+    'aria-haspopup': 'dialog';
+};
+type __VLS_Slots = {
+    /** What the alert says. */
+    default(): unknown;
+    /** Replaces the title and subtitle block with content of your own. */
+    header?(): unknown;
+    /**
+     * The buttons that answer the alert. They are not optional: nothing else can close
+     * this dialog.
+     */
+    footer?(): unknown;
+    /**
+     * The button that opens the alert. Bind the `triggerProps` it receives onto it.
+     */
+    trigger?(props: {
+        triggerProps: TriggerProps;
+    }): unknown;
+};
+type __VLS_ModelProps = {
+    'open'?: boolean;
+};
+type __VLS_PublicProps = __VLS_Props & __VLS_ModelProps;
+declare const __VLS_base: import('vue').DefineComponent<__VLS_PublicProps, {}, {}, {}, {}, import('vue').ComponentOptionsMixin, import('vue').ComponentOptionsMixin, {
+    "update:open": (value: boolean) => any;
+}, string, import('vue').PublicProps, Readonly<__VLS_PublicProps> & Readonly<{
+    "onUpdate:open"?: ((value: boolean) => any) | undefined;
+}>, {
+    title: string;
+    subtitle: string;
+    width: string;
+}, {}, {}, {}, string, import('vue').ComponentProvideOptions, false, {}, any>;
+declare const __VLS_export: __VLS_WithSlots<typeof __VLS_base, __VLS_Slots>;
+declare const _default: typeof __VLS_export;
+export default _default;
+type __VLS_WithSlots<T, S> = T & {
+    new (): {
+        $slots: S;
+    };
+};

package/dist/components/VDialog/VDialogAlert.js

@@ -0,0 +1,7 @@
+import e from "./VDialogAlert.vue_vue_type_script_setup_true_lang.js";
+//#region src/components/VDialog/VDialogAlert.vue
+var t = e;
+//#endregion
+export { t as default };
+
+//# sourceMappingURL=VDialogAlert.js.map

package/dist/components/VDialog/VDialogAlert.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"VDialogAlert.js","names":[],"sources":["../../../src/components/VDialog/VDialogAlert.vue"],"sourcesContent":["<script setup lang=\"ts\">\nimport VDialog from './VDialog.vue'\n\n/**\n * A dialog demanding an answer: confirming something irreversible, acknowledging a\n * failure. It looks exactly like VDialog and is nothing more than VDialog with its\n * options fixed, but those fixed options change what it is.\n *\n * It is announced to assistive technology as an alert rather than an ordinary dialog,\n * and every casual way out is closed off: there is no cross, a click outside does\n * nothing, and Escape does nothing either. The buttons in the footer are the only way\n * to dismiss it — which is why supplying them is not optional.\n */\ninterface DialogAlertProps {\n  /**\n   * The question being asked, which also names the dialog for assistive technology.\n   * It is ignored when the `#header` slot replaces the whole header.\n   */\n  title?: string\n  /** A line under the title, spelling out the consequences of the answer. */\n  subtitle?: string\n  /**\n   * How wide the dialog is, in any CSS unit. It is never allowed to exceed the width\n   * of the viewport.\n   */\n  width?: string\n}\n\nwithDefaults(defineProps<DialogAlertProps>(), {\n  title: undefined,\n  subtitle: undefined,\n  width: '400px',\n})\n\nconst open = defineModel<boolean>('open', { default: false })\n\ntype TriggerProps = {\n  onClick: () => void\n  'aria-haspopup': 'dialog'\n}\n\ndefineSlots<{\n  /** What the alert says. */\n  default(): unknown\n  /** Replaces the title and subtitle block with content of your own. */\n  header?(): unknown\n  /**\n   * The buttons that answer the alert. They are not optional: nothing else can close\n   * this dialog.\n   */\n  footer?(): unknown\n  /**\n   * The button that opens the alert. Bind the `triggerProps` it receives onto it.\n   */\n  trigger?(props: { triggerProps: TriggerProps }): unknown\n}>()\n</script>\n\n<template>\n  <VDialog\n    v-model:open=\"open\"\n    role=\"alertdialog\"\n    :title=\"title\"\n    :subtitle=\"subtitle\"\n    :width=\"width\"\n    :closable=\"false\"\n    :close-on-backdrop=\"false\"\n    :close-on-escape=\"false\"\n  >\n    <template v-if=\"$slots.trigger\" #trigger=\"{ triggerProps }\">\n      <slot name=\"trigger\" :trigger-props=\"triggerProps\" />\n    </template>\n    <template v-if=\"$slots.header\" #header>\n      <slot name=\"header\" />\n    </template>\n    <slot />\n    <template v-if=\"$slots.footer\" #footer>\n      <slot name=\"footer\" />\n    </template>\n  </VDialog>\n</template>\n"],"mappings":""}

package/dist/components/VDialog/VDialogAlert.vue_vue_type_script_setup_true_lang.js

@@ -0,0 +1,60 @@
+import e from "./VDialog.js";
+import { createBlock as t, createSlots as n, defineComponent as r, mergeModels as i, openBlock as a, renderSlot as o, useModel as s, withCtx as c } from "vue";
+//#region src/components/VDialog/VDialogAlert.vue?vue&type=script&setup=true&lang.ts
+var l = /*@__PURE__*/ r({
+	__name: "VDialogAlert",
+	props: /*@__PURE__*/ i({
+		title: { default: void 0 },
+		subtitle: { default: void 0 },
+		width: { default: "400px" }
+	}, {
+		open: {
+			type: Boolean,
+			default: !1
+		},
+		openModifiers: {}
+	}),
+	emits: ["update:open"],
+	setup(r) {
+		let i = s(r, "open");
+		return (s, l) => (a(), t(e, {
+			open: i.value,
+			"onUpdate:open": l[0] ||= (e) => i.value = e,
+			role: "alertdialog",
+			title: r.title,
+			subtitle: r.subtitle,
+			width: r.width,
+			closable: !1,
+			"close-on-backdrop": !1,
+			"close-on-escape": !1
+		}, n({
+			default: c(() => [o(s.$slots, "default")]),
+			_: 2
+		}, [
+			s.$slots.trigger ? {
+				name: "trigger",
+				fn: c(({ triggerProps: e }) => [o(s.$slots, "trigger", { triggerProps: e })]),
+				key: "0"
+			} : void 0,
+			s.$slots.header ? {
+				name: "header",
+				fn: c(() => [o(s.$slots, "header")]),
+				key: "1"
+			} : void 0,
+			s.$slots.footer ? {
+				name: "footer",
+				fn: c(() => [o(s.$slots, "footer")]),
+				key: "2"
+			} : void 0
+		]), 1032, [
+			"open",
+			"title",
+			"subtitle",
+			"width"
+		]));
+	}
+});
+//#endregion
+export { l as default };
+
+//# sourceMappingURL=VDialogAlert.vue_vue_type_script_setup_true_lang.js.map

package/dist/components/VDialog/VDialogAlert.vue_vue_type_script_setup_true_lang.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"VDialogAlert.vue_vue_type_script_setup_true_lang.js","names":["$slots"],"sources":["../../../src/components/VDialog/VDialogAlert.vue"],"sourcesContent":["<script setup lang=\"ts\">\nimport VDialog from './VDialog.vue'\n\n/**\n * A dialog demanding an answer: confirming something irreversible, acknowledging a\n * failure. It looks exactly like VDialog and is nothing more than VDialog with its\n * options fixed, but those fixed options change what it is.\n *\n * It is announced to assistive technology as an alert rather than an ordinary dialog,\n * and every casual way out is closed off: there is no cross, a click outside does\n * nothing, and Escape does nothing either. The buttons in the footer are the only way\n * to dismiss it — which is why supplying them is not optional.\n */\ninterface DialogAlertProps {\n  /**\n   * The question being asked, which also names the dialog for assistive technology.\n   * It is ignored when the `#header` slot replaces the whole header.\n   */\n  title?: string\n  /** A line under the title, spelling out the consequences of the answer. */\n  subtitle?: string\n  /**\n   * How wide the dialog is, in any CSS unit. It is never allowed to exceed the width\n   * of the viewport.\n   */\n  width?: string\n}\n\nwithDefaults(defineProps<DialogAlertProps>(), {\n  title: undefined,\n  subtitle: undefined,\n  width: '400px',\n})\n\nconst open = defineModel<boolean>('open', { default: false })\n\ntype TriggerProps = {\n  onClick: () => void\n  'aria-haspopup': 'dialog'\n}\n\ndefineSlots<{\n  /** What the alert says. */\n  default(): unknown\n  /** Replaces the title and subtitle block with content of your own. */\n  header?(): unknown\n  /**\n   * The buttons that answer the alert. They are not optional: nothing else can close\n   * this dialog.\n   */\n  footer?(): unknown\n  /**\n   * The button that opens the alert. Bind the `triggerProps` it receives onto it.\n   */\n  trigger?(props: { triggerProps: TriggerProps }): unknown\n}>()\n</script>\n\n<template>\n  <VDialog\n    v-model:open=\"open\"\n    role=\"alertdialog\"\n    :title=\"title\"\n    :subtitle=\"subtitle\"\n    :width=\"width\"\n    :closable=\"false\"\n    :close-on-backdrop=\"false\"\n    :close-on-escape=\"false\"\n  >\n    <template v-if=\"$slots.trigger\" #trigger=\"{ triggerProps }\">\n      <slot name=\"trigger\" :trigger-props=\"triggerProps\" />\n    </template>\n    <template v-if=\"$slots.header\" #header>\n      <slot name=\"header\" />\n    </template>\n    <slot />\n    <template v-if=\"$slots.footer\" #footer>\n      <slot name=\"footer\" />\n    </template>\n  </VDialog>\n</template>\n"],"mappings":";;;;;;;;;;;;;;;;;;EAkCA,IAAM,IAAO,EAAoB,GAAC,MAA0B;yBAyB1D,EAoBU,GAAA;GAnBA,MAAM,EAAA;sCAAI,QAAA;GAClB,MAAK;GACJ,OAAO,EAAA;GACP,UAAU,EAAA;GACV,OAAO,EAAA;GACP,UAAU;GACV,qBAAmB;GACnB,mBAAiB;;oBAQV,CAAR,EAAQ,EAAA,QAAA,SAAA,CAAA,CAAA;;;GANQA,EAAAA,OAAO,UAAA;UAAU;WACsB,EADX,sBAAY,CACtD,EAAqD,EAAA,QAAA,WAAA,EAAhB,gBAAY,CAAA,CAAA,CAAA;;;GAEnCA,EAAAA,OAAO,SAAA;UAAS;gBACR,CAAtB,EAAsB,EAAA,QAAA,QAAA,CAAA,CAAA;;;GAGRA,EAAAA,OAAO,SAAA;UAAS;gBACR,CAAtB,EAAsB,EAAA,QAAA,QAAA,CAAA,CAAA"}

package/dist/components/VFileInput/VFileInput.css

@@ -0,0 +1,2 @@
+@layer vectis.reset, vectis.tokens, vectis.components, vectis.utilities;
+@layer vectis.components{.v-file-input{gap:var(--vectis-space-1);width:100%;font-family:var(--vectis-text-family);flex-direction:column;display:flex;position:relative}.v-file-input-native{opacity:0;pointer-events:none;block-size:0;inline-size:0;position:absolute}.v-file-input:not([data-disabled]):not([data-readonly]) .v-file-input-control,.v-file-input:not([data-disabled]):not([data-readonly])[data-display=text] .v-input-control{cursor:pointer}.v-file-input[data-display=text] .v-input-control{text-overflow:ellipsis}.v-file-input[data-dragging] .v-input-field{--field-border-color:var(--vectis-color-accent);background:var(--vectis-color-accent-surface)}.v-file-input[data-display=chip] .v-input-field{height:auto;min-height:var(--control-height);padding-block:var(--vectis-space-1);flex-wrap:wrap;padding-inline-end:calc(var(--control-padding-inline-field) + var(--vectis-icon-size) + var(--control-gap));position:relative}.v-file-input[data-display=chip][data-can-clear] .v-input-field{padding-inline-end:calc(var(--control-padding-inline-field) + 2 * var(--vectis-icon-size) + 2 * var(--control-gap))}.v-file-input[data-display=chip] .v-input-control{height:var(--chip-height)}.v-file-input[data-display=chip] .v-input-clear,.v-file-input[data-display=chip] .v-input-action:not(.v-input-clear){position:absolute;top:50%;translate:0 -50%}.v-file-input[data-display=chip] .v-input-action:not(.v-input-clear){inset-inline-end:var(--control-padding-inline-field)}.v-file-input[data-display=chip] .v-input-clear{inset-inline-end:calc(var(--control-padding-inline-field) + var(--vectis-icon-size) + var(--control-gap))}.v-file-input-meta{align-items:baseline;gap:var(--vectis-space-2);display:flex}.v-file-input-counter{font-size:var(--vectis-text-caption-size);color:var(--vectis-color-text-muted);font-variant-numeric:tabular-nums;margin-inline-start:auto}.v-file-input[data-disabled] .v-file-input-hint,.v-file-input[data-disabled] .v-file-input-counter{color:var(--vectis-color-text-subtle)}}