vectis-ui 0.8.1 → 0.9.0

package/dist/components/VSlider/VSlider.js.map

@@ -1 +1 @@
-{"version":3,"file":"VSlider.js","names":[],"sources":["../../../src/components/VSlider/VSlider.vue"],"sourcesContent":["<script setup lang=\"ts\">\n// @core\n/**\n * A value chosen by sliding a thumb along a track, optionally a range between two.\n *\n * Underneath is a native `<input type=\"range\">`, which brings the keyboard, the ARIA and the\n * form behaviour. The JS covers only what it cannot: stopping the two values crossing —\n * there is no native two-thumb control, so a range is two superimposed — refusing a change\n * when `readonly`, which a range input has no native form of, feeding the optional number\n * fields, and computing the positions of the ticks and labels.\n *\n * Those positions reach the stylesheet as unitless inline fractions, and that is the whole\n * binding between the two. They matter because a thumb's CENTRE does not travel the full\n * width of the track: it runs from half a thumb in to half a thumb from the end, and\n * everything meant to line up with it has to follow that same run.\n */\n\nimport { computed, inject, ref, watch } from 'vue'\nimport VIcon from '../VIcon/VIcon.vue'\nimport { iconProps } from '../VIcon/iconProps'\nimport type { IconSource } from '../VIcon/types'\nimport VInput from '../VInput/VInput.vue'\nimport { inputGroupKey } from '../VInput/context'\n\nimport { useControlShape } from '../../composables/useControlShape'\nimport { useRootAttrs } from '../../composables/useRootAttrs'\nimport { isDev } from '../../utils/env'\nimport { clamp } from '../../utils/number'\nimport { useMessages } from '../../i18n/state'\n\nexport type SliderLabel = string | { icon: IconSource; label: string }\n\n/** The value of a slider: one number, or an ordered pair of them in range mode. */\nexport type SliderValue = number | [number, number]\n\n/** Which way the track runs. */\nexport type SliderOrientation = 'horizontal' | 'vertical'\n\n/** The height of the number fields: 32, 40 or 48 pixels. */\nexport type SliderSize = 'sm' | 'md' | 'lg'\n\ninterface SliderProps {\n  /** The lowest value the thumb can reach. It is 0 by default. */\n  min?: number\n  /** The highest value the thumb can reach. It is 100 by default. */\n  max?: number\n  /**\n   * The gap between two values the thumb can stop on, 1 by default. It is also what the\n   * arrow keys move by, and what a value typed into the companion field is snapped to.\n   */\n  step?: number\n  /** Offers two thumbs to pick a range, which makes the v-model a pair of values. */\n  range?: boolean\n  /** Makes the slider unusable. */\n  disabled?: boolean\n  /**\n   * Shows the value without allowing it to be changed. The thumbs can still be focused and\n   * are announced as read-only, but neither the pointer nor the keyboard moves them, and the\n   * number fields turn read-only with them.\n   */\n  readonly?: boolean\n  /**\n   * Marks the value as invalid, which colours the thumbs and tells assistive technology\n   * so. It is for a rule the browser cannot check by itself.\n   */\n  invalid?: boolean\n  /**\n   * The height of the number fields `inputs` adds. Inside a VInputGroup the group's size\n   * wins, as it does for every field of the row.\n   */\n  size?: SliderSize\n  /**\n   * What screen readers announce for the slider. It is an accessible name and draws\n   * nothing on screen. In range mode the two thumbs are announced as the start and the\n   * end of it.\n   */\n  label?: string\n  /** Turns the slider upright, with the lowest value at the bottom. */\n  orientation?: SliderOrientation\n  /**\n   * Adds a number field beside the slider for setting the value exactly — one, or one\n   * per end in range mode. Sliding is quick but imprecise; this is the way out.\n   */\n  inputs?: boolean\n  /**\n   * Marks each step on the track. Providing labels implies it. Past fifty steps the\n   * marks would be an unreadable comb and are not drawn at all.\n   */\n  ticks?: boolean\n  /**\n   * A label for every step, in order — a piece of text, or an icon with the words that\n   * name it for screen readers. They also become what a screen reader announces in\n   * place of the raw number.\n   */\n  labels?: SliderLabel[]\n  /** Shows the value in a bubble above the thumb while it is being moved or focused. */\n  tooltip?: boolean\n}\n\nconst props = withDefaults(defineProps<SliderProps>(), {\n  min: 0,\n  max: 100,\n  step: 1,\n  range: false,\n  disabled: false,\n  readonly: false,\n  invalid: false,\n  size: 'md',\n  label: undefined,\n  orientation: 'horizontal',\n  inputs: false,\n  ticks: false,\n  labels: undefined,\n  tooltip: false,\n})\n\n/**\n * The value, and its SHAPE is what puts the slider in range mode: a single number — 0 to\n * begin with — gives one thumb, a pair of them gives two. The pair is always ordered, the\n * thumbs being stopped from crossing.\n */\nconst model = defineModel<SliderValue>({ default: 0 })\n\nconst emit = defineEmits<{\n  /**\n   * The reader has SETTLED on a value: a thumb was released or moved by a key, or a number\n   * field was committed. It carries the whole value, a pair in range mode, and fires for\n   * either thumb, where the v-model follows every step of a drag.\n   */\n  change: [value: SliderValue]\n}>()\n\n// The number fields are fields of a VInputGroup row like any other, so the row's size and\n// its disabled state reach them through the same arbitration. A slider has no `compact` of\n// its own: only the row's can apply.\nconst group = inject(inputGroupKey, null)\nconst {\n  size: resolvedSize,\n  compact: resolvedCompact,\n  disabled: resolvedDisabled,\n} = useControlShape(\n  {\n    get size() {\n      return props.size\n    },\n    compact: false,\n    get disabled() {\n      return props.disabled\n    },\n  },\n  group,\n)\n\ntype Thumb = 'start' | 'end'\n\nconst startValue = computed(() => (Array.isArray(model.value) ? model.value[0] : props.min))\nconst endValue = computed(() =>\n  Array.isArray(model.value) ? model.value[1] : (model.value as number),\n)\n\nconst thumbValue = (which: Thumb) => (which === 'start' ? startValue.value : endValue.value)\n\n/**\n * Where a value sits along the run, as a fraction between 0 and 1. The guard covers a\n * slider whose two bounds are equal, which would otherwise divide by zero.\n */\nconst frac = (v: number) => clamp((v - props.min) / (props.max - props.min || 1), 0, 1)\n\n// @core — the ONE place a thumb is written, so what stops the two values crossing exists\n// once for the thumbs and the number fields alike. A range is two native controls laid over\n// one another, and there is no dual-thumb control to inherit this behaviour from. It returns\n// what was written, which is what each caller reads back: a model that lags a parent\n// `v-model` would still hold the value from before.\nfunction writeThumb(which: Thumb, n: number): SliderValue {\n  const next: SliderValue = !props.range\n    ? n\n    : which === 'start'\n      ? [Math.min(n, endValue.value), endValue.value]\n      : [startValue.value, Math.max(n, startValue.value)]\n  model.value = next\n  return next\n}\n\nconst writtenFor = (value: SliderValue, which: Thumb) =>\n  Array.isArray(value) ? value[which === 'start' ? 0 : 1] : value\n\nfunction onThumbInput(which: Thumb, event: Event) {\n  const el = event.target as HTMLInputElement\n  // @core\n  // A drag or a click on the track has ALREADY moved the native thumb when `input` fires,\n  // and the event cannot be cancelled: putting the value back is the only refusal there is.\n  // It lands before the browser paints, so the thumb never visibly leaves its place, and\n  // since the value at release is the one it started from, no `change` follows either.\n  if (props.readonly) {\n    el.value = String(thumbValue(which))\n    return\n  }\n  // Written back to the DOM as well: a thumb dragged past its sibling stops against it.\n  el.value = String(writtenFor(writeThumb(which, Number(el.value)), which))\n}\n\n// @keyboard @core\n// The keys that move a range input, cancelled before the browser applies them when the\n// slider is read-only. Tab and every other key pass, so the thumbs stay reachable.\nconst VALUE_KEYS = new Set([\n  'ArrowUp',\n  'ArrowDown',\n  'ArrowLeft',\n  'ArrowRight',\n  'Home',\n  'End',\n  'PageUp',\n  'PageDown',\n])\n\nfunction onThumbKeydown(event: KeyboardEvent) {\n  if (props.readonly && VALUE_KEYS.has(event.key)) event.preventDefault()\n}\n\n// @core\n/*\n * A range is two native controls, and a consumer's `@change` could only ever reach ONE of\n * them through the forwarded attributes: moving the start thumb told nobody. So `change` is\n * declared and fed by both.\n *\n * TRAP — the settled value is read off the THUMB, never off the model. A key press fires\n * `input` and `change` back to back in one task, and under a parent `v-model` the model's\n * local copy only catches up when the parent re-renders, so it would still hold the value\n * from before the key.\n */\nfunction onThumbChange(which: Thumb, event: Event) {\n  if (props.readonly) return\n  const value = Number((event.target as HTMLInputElement).value)\n  if (!props.range) emit('change', value)\n  else emit('change', which === 'start' ? [value, endValue.value] : [startValue.value, value])\n}\n\n/**\n * How many whole steps the thumb can actually stop on. It matters when the range does\n * not divide evenly by the step: the native control stops at the last step that fits,\n * short of the maximum, and the ticks have to agree with it.\n */\nconst stepCount = computed(() => Math.floor((props.max - props.min) / props.step + 1e-9))\n\nconst showTicks = computed(\n  () =>\n    (props.ticks || props.labels !== undefined) && stepCount.value >= 1 && stepCount.value <= 50,\n)\n\n/**\n * Each step's value and the style that places it, shared by the ticks and the labels. Only\n * the bounds and the step move them, so dragging a thumb rebuilds none of it: each style\n * object keeps its identity from one render to the next, and Vue skips a binding whose\n * object has not changed. Which ticks are FILLED does follow the value, and is asked\n * separately, in `isFilled`.\n */\nconst stepPlaces = computed(() => {\n  const length = Math.max(showTicks.value ? stepCount.value + 1 : 0, props.labels?.length ?? 0)\n  return Array.from({ length }, (_, i) => {\n    const value = props.min + i * props.step\n    return { value, style: { '--fill-fraction': String(frac(value)) } }\n  })\n})\n\nconst tickPlaces = computed(() =>\n  showTicks.value ? stepPlaces.value.slice(0, stepCount.value + 1) : [],\n)\n\nconst isFilled = (value: number) =>\n  props.range ? value >= startValue.value && value <= endValue.value : value <= endValue.value\n\n/** What a value is called, if the consumer named its step; failing that, the number itself. */\nfunction labelTextAt(value: number): string {\n  const item = props.labels?.[Math.round((value - props.min) / props.step)]\n  if (item === undefined) return String(value)\n  return typeof item === 'string' ? item : item.label\n}\n\n// @a11y\n/* What each thumb is announced as. There is no prop for the two halves: the wording\n   comes from the dictionary, which is also where it is changed.\n\n   With a single thumb there is nothing to distinguish: that thumb IS the value, so it\n   simply takes the consumer's label, and is left unnamed when none was given. The\n   generic fallback applies to the NUMBER FIELD alone, which cannot go unnamed — a bare\n   field in a form has to say what it holds. */\nconst m = useMessages()\nconst startLabel = computed(() =>\n  props.label ? m.value.slider.rangeStart(props.label) : m.value.slider.start,\n)\nconst endLabel = computed(() =>\n  props.label ? m.value.slider.rangeEnd(props.label) : m.value.slider.end,\n)\nconst thumbEndLabel = computed(() => (props.range ? endLabel.value : props.label))\nconst fieldEndLabel = computed(() =>\n  props.range ? endLabel.value : (props.label ?? m.value.slider.value),\n)\n\nconst startValueText = computed(() =>\n  props.range && props.labels ? labelTextAt(startValue.value) : undefined,\n)\nconst endValueText = computed(() => (props.labels ? labelTextAt(endValue.value) : undefined))\n\n// @a11y\n/*\n * The wrapper-root split. The root here is a layout box holding the labels, the track and\n * the optional number fields, so a consumer's `name`, `id`, `required` and `aria-*` have\n * to be redirected onto the real `<input type=\"range\">` — left on the wrapper, a `name`\n * submits nothing and a `<label for>` points at a div.\n *\n * They go to the END thumb, which is the one always rendered. A RANGE has two thumbs and\n * therefore no single value to submit, which the warning below says out loud rather than\n * letting a form come back with half the answer.\n */\ndefineOptions({ inheritAttrs: false })\nconst { attrs, rootClass, rootStyle, forwardedAttrs } = useRootAttrs()\n\n// @devwarn\nif (isDev) {\n  if ((props.ticks || props.labels) && stepCount.value > 50)\n    console.warn(`[VSlider] ${stepCount.value} steps — ticks/labels not rendered past 50.`)\n  if (props.labels && props.labels.length !== stepCount.value + 1)\n    console.warn(\n      `[VSlider] ${props.labels.length} labels for ${stepCount.value + 1} steps — one label per step expected.`,\n    )\n  if (props.range && attrs.name !== undefined)\n    console.warn(\n      `[VSlider] name=\"${String(attrs.name)}\" on a range: only the end thumb carries it, so the form receives one value of the two. Bind the model to two inputs of your own instead.`,\n    )\n}\n\n// The text held by the number fields, kept apart from the slider's own value.\n//\n// It is typed as text OR a number because these are number fields, whose value Vue\n// converts to a number as soon as it can be read as one — while an empty field, or one\n// holding a half-typed \"1-\", stays text. That is why the value is turned back into text\n// when it is committed. The start field exists in range mode only, and so does its sync.\nconst startFieldText = ref<string | number>(String(startValue.value))\nconst endFieldText = ref<string | number>(String(endValue.value))\n\n// Sliding the thumb keeps the fields in step, continuously.\nwatch(startValue, (v) => {\n  if (props.range) startFieldText.value = String(v)\n})\nwatch(endValue, (v) => (endFieldText.value = String(v)))\n\n/**\n * Takes what was typed in a field and makes it the value — but only once the reader has\n * finished, on leaving the field or on Enter. Reading it as they type would clamp the\n * \"1\" of \"15\" to the minimum before the 5 was ever pressed.\n *\n * Anything unreadable, an empty field included, silently puts the previous value back.\n */\nfunction commitField(which: Thumb) {\n  const raw = which === 'start' ? startFieldText.value : endFieldText.value\n  // TRAP — parsed rather than converted: an empty string parses to nothing, which is\n  // what triggers the revert below, where converting it would give ZERO and quietly\n  // overwrite the value with it.\n  const parsed = Number.parseFloat(String(raw))\n  if (Number.isNaN(parsed)) {\n    resyncFields()\n    return\n  }\n  // Brought onto the nearest step. The rounding that follows removes the noise decimal\n  // steps leave behind — a tenth cannot be represented exactly, so 0.1 × 3 comes out as\n  // 0.30000000000000004.\n  const clamped = clamp(parsed, props.min, props.max)\n  let value = props.min + Math.round((clamped - props.min) / props.step) * props.step\n  value = Math.min(props.max, Math.round(value * 1e10) / 1e10)\n  const previous = thumbValue(which)\n  const next = writeThumb(which, value)\n  // Emitted only when the value MOVED, as a native range emits nothing for a key that\n  // cannot move its thumb — and the payload is `next`, the model's local copy lagging a\n  // parent `v-model` (see `onThumbChange`).\n  if (writtenFor(next, which) !== previous) emit('change', next)\n  // Put back explicitly, because a commit that does not change the value — typing 200\n  // where the maximum is 100 — changes nothing for the watchers to react to, and the\n  // field would go on showing what was typed.\n  resyncFields()\n}\n\nfunction resyncFields() {\n  if (props.range) startFieldText.value = String(startValue.value)\n  endFieldText.value = String(endValue.value)\n}\n\nconst endThumbEl = ref<HTMLInputElement | null>(null)\n\n// The root is a layout box, so a template ref on the component reaches the wrapper and not\n// the control. Both members point at the END thumb: it is the one always rendered, and the\n// one the consumer's `id` lands on, so `focus()` goes where a `<label for>` would send it.\ndefineExpose({\n  /** Moves the focus to the end thumb, the only thumb outside range mode. */\n  focus: (options?: FocusOptions) => endThumbEl.value?.focus(options),\n  /** The end thumb's real `<input type=\"range\">`, for what `focus` does not cover. */\n  el: endThumbEl,\n})\n</script>\n\n<template>\n  <div\n    class=\"v-slider\"\n    :class=\"rootClass\"\n    :data-range=\"range ? '' : undefined\"\n    :data-disabled=\"resolvedDisabled ? '' : undefined\"\n    :data-readonly=\"readonly ? '' : undefined\"\n    :data-invalid=\"invalid ? '' : undefined\"\n    :data-size=\"resolvedSize\"\n    :data-orientation=\"orientation\"\n    :style=\"[\n      rootStyle,\n      {\n        '--start-fraction': range ? String(frac(startValue)) : undefined,\n        '--end-fraction': String(frac(endValue)),\n      },\n    ]\"\n  >\n    <VInput\n      v-if=\"inputs && range\"\n      v-model=\"startFieldText\"\n      class=\"v-slider-field v-slider-field-start\"\n      type=\"number\"\n      :size=\"resolvedSize\"\n      :compact=\"resolvedCompact\"\n      :min=\"min\"\n      :max=\"max\"\n      :step=\"step\"\n      :disabled=\"resolvedDisabled\"\n      :readonly=\"readonly\"\n      :invalid=\"invalid\"\n      :aria-label=\"startLabel\"\n      @change=\"commitField('start')\"\n    />\n    <div class=\"v-slider-rail\">\n      <span class=\"v-slider-control\">\n        <span class=\"v-slider-track\" aria-hidden=\"true\">\n          <span class=\"v-slider-fill\" />\n          <span\n            v-for=\"(tick, i) in tickPlaces\"\n            :key=\"i\"\n            class=\"v-slider-tick\"\n            :data-filled=\"isFilled(tick.value) ? '' : undefined\"\n            :style=\"tick.style\"\n          />\n        </span>\n        <input\n          v-if=\"range\"\n          type=\"range\"\n          class=\"v-slider-input v-slider-input-start\"\n          :min=\"min\"\n          :max=\"max\"\n          :step=\"step\"\n          :disabled=\"resolvedDisabled\"\n          :value=\"startValue\"\n          :aria-label=\"startLabel\"\n          :aria-valuetext=\"startValueText\"\n          :aria-invalid=\"invalid || undefined\"\n          :aria-readonly=\"readonly || undefined\"\n          @keydown=\"onThumbKeydown\"\n          @input=\"onThumbInput('start', $event)\"\n          @change=\"onThumbChange('start', $event)\"\n        />\n        <!-- The consumer's attributes come FIRST, so what the component decides for\n             itself — the bounds, the value, the disabled state and the thumb's own\n             accessible name — cannot be overwritten by one of them. Naming a slider\n             goes through the `label` prop, which is what gives each thumb of a range a\n             name of its own. -->\n        <input\n          ref=\"endThumbEl\"\n          v-bind=\"forwardedAttrs\"\n          type=\"range\"\n          class=\"v-slider-input v-slider-input-end\"\n          :min=\"min\"\n          :max=\"max\"\n          :step=\"step\"\n          :disabled=\"resolvedDisabled\"\n          :value=\"endValue\"\n          :aria-label=\"thumbEndLabel\"\n          :aria-valuetext=\"endValueText\"\n          :aria-invalid=\"invalid || undefined\"\n          :aria-readonly=\"readonly || undefined\"\n          @keydown=\"onThumbKeydown\"\n          @input=\"onThumbInput('end', $event)\"\n          @change=\"onThumbChange('end', $event)\"\n        />\n      </span>\n      <span\n        v-if=\"tooltip && range\"\n        class=\"v-slider-tooltip v-slider-tooltip-start\"\n        aria-hidden=\"true\"\n      >\n        <span class=\"v-slider-tooltip-bubble\">{{ startValueText ?? startValue }}</span>\n      </span>\n      <span v-if=\"tooltip\" class=\"v-slider-tooltip v-slider-tooltip-end\" aria-hidden=\"true\">\n        <span class=\"v-slider-tooltip-bubble\">{{ endValueText ?? endValue }}</span>\n      </span>\n    </div>\n    <div v-if=\"labels\" class=\"v-slider-labels\">\n      <span\n        v-for=\"(item, i) in labels\"\n        :key=\"i\"\n        class=\"v-slider-label\"\n        :style=\"stepPlaces[i]?.style\"\n      >\n        <template v-if=\"typeof item === 'string'\">{{ item }}</template>\n        <VIcon v-else v-bind=\"iconProps(item.icon)\" :label=\"item.label\" />\n      </span>\n    </div>\n    <VInput\n      v-if=\"inputs\"\n      v-model=\"endFieldText\"\n      class=\"v-slider-field v-slider-field-end\"\n      type=\"number\"\n      :size=\"resolvedSize\"\n      :compact=\"resolvedCompact\"\n      :min=\"min\"\n      :max=\"max\"\n      :step=\"step\"\n      :disabled=\"resolvedDisabled\"\n      :readonly=\"readonly\"\n      :invalid=\"invalid\"\n      :aria-label=\"fieldEndLabel\"\n      @change=\"commitField('end')\"\n    />\n  </div>\n</template>\n\n<style>\n@layer vectis.components {\n  .v-slider {\n    --slider-thumb: var(--vectis-control-size-slider-thumb);\n    --slider-track: var(--vectis-control-size-slider-track);\n    display: grid;\n    grid-template-areas: 'rail';\n    grid-template-columns: minmax(0, 1fr);\n    align-items: center;\n    column-gap: var(--vectis-space-2);\n    row-gap: var(--vectis-space-1);\n    width: 100%;\n    font-family: var(--vectis-text-family);\n  }\n\n  /*\n     The zones the root lays out, from least to most furnished. `:has()` takes the\n     specificity of its argument, so the single-condition rules are all (0,2,0) and the\n     two-condition ones (0,3,0) — which means the five below are arbitrated by SOURCE\n     ORDER as much as by weight, and a range slider with inputs matches three of them at\n     once. They must stay in this order, each configuration overwriting the poorer one it\n     builds on. Alphabetize them, or move `field-start` above `field-end`, and the start\n     field lands outside the grid: no error, just a control sitting where nothing put it. */\n  .v-slider:has(.v-slider-labels) {\n    grid-template-areas: 'rail' 'labels';\n  }\n\n  .v-slider:has(.v-slider-field-end) {\n    grid-template-areas: 'rail field-end';\n    grid-template-columns: minmax(0, 1fr) auto;\n  }\n\n  .v-slider:has(.v-slider-field-end):has(.v-slider-labels) {\n    grid-template-areas: 'rail field-end' 'labels .';\n  }\n\n  .v-slider:has(.v-slider-field-start) {\n    grid-template-areas: 'field-start rail field-end';\n    grid-template-columns: auto minmax(0, 1fr) auto;\n  }\n\n  .v-slider:has(.v-slider-field-start):has(.v-slider-labels) {\n    grid-template-areas: 'field-start rail field-end' '. labels .';\n  }\n\n  .v-slider-rail {\n    grid-area: rail;\n    position: relative;\n    block-size: var(--slider-thumb);\n  }\n\n  .v-slider-control {\n    position: absolute;\n    inset: 0;\n  }\n\n  .v-slider-track {\n    position: absolute;\n    inset-inline: 0;\n    inset-block: 0;\n    margin-block: auto;\n    block-size: var(--slider-track);\n    border-radius: var(--vectis-radius-pill);\n    background: var(--vectis-color-border);\n    overflow: hidden;\n  }\n\n  /*\n     Where a thumb's CENTRE sits for the fraction `--fill-fraction`, written once for every\n     element lined up with it: half a thumb in, then the fraction of the run that is left.\n\n     TRAP — it must be declared on the element that CARRIES the fraction, never on an\n     ancestor. A custom property's `var()` is resolved where the property is declared, so\n     set on the root it would read a `--fill-fraction` the root does not have and turn\n     invalid, and every tick, label and bubble would drop to its static position at the\n     start of the track, with no error. The `100%`, on the other hand, stays a percentage\n     until it is used, and resolves against the box of the property that reads it — the\n     inline size of the track for an inset, the block size in the vertical rules. */\n  .v-slider-fill,\n  .v-slider-tick,\n  .v-slider-tooltip,\n  .v-slider-label {\n    --slider-at: calc(\n      var(--slider-thumb) / 2 + (100% - var(--slider-thumb)) * var(--fill-fraction)\n    );\n  }\n\n  .v-slider-fill {\n    --fill-fraction: var(--end-fraction);\n    position: absolute;\n    inset-block: 0;\n    inset-inline-start: 0;\n    inline-size: var(--slider-at);\n    background: var(--vectis-color-accent);\n  }\n\n  .v-slider[data-range] .v-slider-fill {\n    --fill-fraction: var(--start-fraction);\n    inset-inline-start: var(--slider-at);\n    inline-size: calc((100% - var(--slider-thumb)) * (var(--end-fraction) - var(--start-fraction)));\n  }\n\n  .v-slider-tick {\n    --slider-tick: calc(var(--slider-track) / 3 * 2);\n    position: absolute;\n    inset-block: 0;\n    margin-block: auto;\n    inset-inline-start: calc(var(--slider-at) - var(--slider-tick) / 2);\n    inline-size: var(--slider-tick);\n    block-size: var(--slider-tick);\n    border-radius: var(--vectis-radius-pill);\n    background: var(--vectis-color-border-strong);\n  }\n\n  .v-slider-tick[data-filled] {\n    background: var(--vectis-color-text-on-accent);\n  }\n\n  /* The two controls lie exactly on top of one another, so only their thumbs are allowed\n     to receive the pointer. Without that, the one on top would swallow every click and\n     the other thumb could never be grabbed.\n\n     The thumb's paint lives in variables set HERE, on the control, and read once by each\n     vendor pseudo-element below. That is what lets every state be written a single time:\n     a state pseudo-class written after the thumb's own pseudo-element is unreliable across\n     browsers, so a state has to be read on the control either way, and the thumb inherits\n     the variables from it.\n\n     The thumb is white in BOTH themes, the VSwitch thumb's colour: on a dark page a thumb\n     painted in `surface` sinks into the track instead of standing out as the handle. */\n  .v-slider-input {\n    --slider-thumb-bg: var(--vectis-color-text-on-accent);\n    --slider-thumb-border: var(--vectis-color-accent);\n    --slider-thumb-shadow: var(--vectis-shadow-xs);\n    --slider-thumb-outline: none;\n    --slider-thumb-cursor: pointer;\n    --slider-thumb-transition: background-color var(--vectis-duration-fast)\n      var(--vectis-ease-default);\n    position: absolute;\n    inset: 0;\n    width: 100%;\n    height: 100%;\n    margin: 0;\n    appearance: none;\n    background: transparent;\n    pointer-events: none;\n  }\n\n  /* With a single thumb there is nothing underneath to protect, so the whole control\n     takes the pointer again — which is what makes clicking the track jump the value\n     there and start dragging at once, natively and with no code at all. The accepted\n     side effect is that the thumb lights up when the pointer is anywhere over the\n     track. */\n  .v-slider:not([data-range]) .v-slider-input {\n    pointer-events: auto;\n    cursor: pointer;\n  }\n\n  /* TRAP — the two vendor pseudo-elements stay in two separate rules. A selector list\n     holding one a browser does not know is dropped WHOLE, so merged, each engine would\n     throw away the other's thumb and draw its native one. */\n  .v-slider-input::-webkit-slider-thumb {\n    appearance: none;\n    pointer-events: auto;\n    width: var(--slider-thumb);\n    height: var(--slider-thumb);\n    border-radius: var(--vectis-radius-pill);\n    background: var(--slider-thumb-bg);\n    border: var(--vectis-control-border-width) solid var(--slider-thumb-border);\n    box-shadow: var(--slider-thumb-shadow);\n    outline: var(--slider-thumb-outline);\n    outline-offset: var(--vectis-focus-ring-offset);\n    cursor: var(--slider-thumb-cursor);\n    transition: var(--slider-thumb-transition);\n  }\n\n  .v-slider-input::-moz-range-thumb {\n    pointer-events: auto;\n    width: var(--slider-thumb);\n    height: var(--slider-thumb);\n    border-radius: var(--vectis-radius-pill);\n    background: var(--slider-thumb-bg);\n    border: var(--vectis-control-border-width) solid var(--slider-thumb-border);\n    box-shadow: var(--slider-thumb-shadow);\n    outline: var(--slider-thumb-outline);\n    outline-offset: var(--vectis-focus-ring-offset);\n    cursor: var(--slider-thumb-cursor);\n    transition: var(--slider-thumb-transition);\n  }\n\n  /* The states, all at (0,3,0) but the base, so their ORDER arbitrates them: hover, then\n     read-only, invalid and disabled, each overriding what came before on a thumb that is\n     several at once.\n\n     The hover tint is mixed from the thumb's own white rather than read from\n     `accent-surface`: that token turns dark in the dark theme, and a white thumb would\n     flash nearly black under the pointer. */\n  .v-slider-input:is(:hover, :active):not(:disabled) {\n    --slider-thumb-bg: color-mix(\n      in oklab,\n      var(--vectis-color-text-on-accent),\n      var(--vectis-color-accent) 10%\n    );\n  }\n\n  .v-slider-input:focus-visible {\n    --slider-thumb-outline: var(--vectis-focus-ring-width) solid var(--vectis-focus-ring-color);\n    outline: none;\n  }\n\n  /* The muted text colour a read-only VCheckbox takes, on the fill and the thumb's ring:\n     the value stays plainly readable, the accent no longer invites a drag. */\n  .v-slider[data-readonly] .v-slider-input {\n    --slider-thumb-bg: var(--vectis-color-surface);\n    --slider-thumb-border: var(--vectis-color-text-muted);\n    --slider-thumb-cursor: default;\n    cursor: default;\n  }\n\n  .v-slider[data-readonly] .v-slider-fill {\n    background: var(--vectis-color-text-muted);\n  }\n\n  .v-slider[data-readonly] .v-slider-tick[data-filled] {\n    background: var(--vectis-color-surface);\n  }\n\n  /* The border colour VCheckbox and VRadio take when invalid, on the thumb's ring. */\n  .v-slider[data-invalid] .v-slider-input {\n    --slider-thumb-border: var(--vectis-color-danger);\n  }\n\n  /* The bubble showing the value. It looks like a VTooltip but is placed by arithmetic\n     rather than anchored to the thumb: a native thumb is a pseudo-element, and the\n     browser's anchoring cannot attach anything to one. The fraction it follows is the one\n     the root already carries for the fill. */\n  .v-slider-tooltip {\n    position: absolute;\n    inset-block-end: calc(100% + var(--vectis-space-2));\n    inset-inline-start: var(--slider-at);\n    inline-size: 0;\n    display: flex;\n    justify-content: center;\n    opacity: 0;\n    visibility: hidden;\n    transition:\n      opacity var(--vectis-duration-fast) var(--vectis-ease-default),\n      visibility var(--vectis-duration-fast) var(--vectis-ease-default);\n  }\n\n  .v-slider-tooltip-start {\n    --fill-fraction: var(--start-fraction);\n  }\n\n  .v-slider-tooltip-end {\n    --fill-fraction: var(--end-fraction);\n  }\n\n  .v-slider:has(.v-slider-input-start:active) .v-slider-tooltip-start,\n  .v-slider:has(.v-slider-input-start:focus-visible) .v-slider-tooltip-start,\n  .v-slider:has(.v-slider-input-end:active) .v-slider-tooltip-end,\n  .v-slider:has(.v-slider-input-end:focus-visible) .v-slider-tooltip-end {\n    opacity: 1;\n    visibility: visible;\n  }\n\n  .v-slider-tooltip-bubble {\n    padding: var(--vectis-space-1) var(--vectis-space-2);\n    background: var(--vectis-color-surface-inverse);\n    color: var(--vectis-color-text-on-inverse);\n    font-size: var(--vectis-text-caption-size);\n    line-height: var(--vectis-text-caption-leading);\n    /* VTooltip's bubble corner, so the two tooltips of the design system stay one shape. */\n    border-radius: min(var(--vectis-radius-interactive), calc(0.5lh + var(--vectis-space-1)));\n    box-shadow: var(--vectis-shadow-sm);\n    white-space: nowrap;\n  }\n\n  .v-slider-labels {\n    grid-area: labels;\n    position: relative;\n    /* The labels are positioned individually and therefore contribute no height of\n       their own; this reserves enough room for either kind, a small line of text or an\n       icon. */\n    min-block-size: var(--vectis-icon-size-md);\n    --vectis-icon-size: var(--vectis-icon-size-md);\n    font-size: var(--vectis-text-caption-size);\n    color: var(--vectis-color-text-muted);\n  }\n\n  /* A box of zero width placed exactly on the step: its content then overflows equally\n     on both sides, which centres it there. Centring it with a transform would be the\n     usual trick, but a transform is physical and would have to be undone for the\n     vertical orientation and again for a right-to-left page. */\n  .v-slider-label {\n    position: absolute;\n    inset-block-start: 0;\n    inset-inline-start: var(--slider-at);\n    inline-size: 0;\n    display: flex;\n    justify-content: center;\n    white-space: nowrap;\n  }\n\n  .v-slider-field.v-input {\n    inline-size: var(--vectis-control-size-slider-field);\n  }\n\n  .v-slider-field-start {\n    grid-area: field-start;\n  }\n\n  .v-slider-field-end {\n    grid-area: field-end;\n  }\n\n  .v-slider[data-orientation='vertical'] {\n    grid-template-areas: 'rail';\n    grid-template-columns: none;\n    inline-size: fit-content;\n    justify-items: center;\n  }\n\n  .v-slider[data-orientation='vertical']:has(.v-slider-labels) {\n    grid-template-areas: 'rail labels';\n    grid-template-columns: auto auto;\n  }\n\n  .v-slider[data-orientation='vertical']:has(.v-slider-field-end) {\n    grid-template-areas: 'field-end' 'rail';\n    grid-template-columns: none;\n  }\n\n  .v-slider[data-orientation='vertical']:has(.v-slider-field-end):has(.v-slider-labels) {\n    grid-template-areas: 'field-end .' 'rail labels';\n    grid-template-columns: auto auto;\n  }\n\n  .v-slider[data-orientation='vertical']:has(.v-slider-field-start) {\n    grid-template-areas: 'field-end' 'rail' 'field-start';\n    grid-template-columns: none;\n  }\n\n  .v-slider[data-orientation='vertical']:has(.v-slider-field-start):has(.v-slider-labels) {\n    grid-template-areas: 'field-end .' 'rail labels' 'field-start .';\n    grid-template-columns: auto auto;\n  }\n\n  .v-slider[data-orientation='vertical'] .v-slider-rail {\n    inline-size: var(--slider-thumb);\n    block-size: var(--vectis-control-size-slider-length);\n  }\n\n  /* Only this inner box is turned upright, and that is the whole trick: the track, the\n     fill and the ticks are all placed with logical properties, so they follow the change\n     of axis with no rule written a second time — while the bubbles and the labels stay\n     outside that box, and therefore keep their text horizontal.\n\n     The direction is reversed with it so that the lowest value ends up at the bottom. */\n  .v-slider[data-orientation='vertical'] .v-slider-control {\n    writing-mode: vertical-lr;\n    direction: rtl;\n  }\n\n  .v-slider[data-orientation='vertical'] .v-slider-tooltip {\n    inset-block-end: var(--slider-at);\n    inset-inline-start: auto;\n    inset-inline-end: calc(100% + var(--vectis-space-2));\n    inline-size: auto;\n    block-size: 0;\n    align-items: center;\n    justify-content: flex-end;\n  }\n\n  .v-slider[data-orientation='vertical'] .v-slider-labels {\n    align-self: stretch;\n    min-block-size: auto;\n  }\n\n  .v-slider[data-orientation='vertical'] .v-slider-label {\n    inset-block-start: auto;\n    inset-block-end: var(--slider-at);\n    inset-inline-start: 0;\n    inline-size: auto;\n    block-size: 0;\n    align-items: center;\n    justify-content: flex-start;\n  }\n\n  /* A disabled slider greys out through the colour tokens, the same ones VCheckbox and\n     VSwitch use, and never through opacity. It comes LAST among the states, so a slider\n     both disabled and read-only or invalid is drawn disabled. */\n  .v-slider[data-disabled] {\n    cursor: not-allowed;\n  }\n\n  .v-slider[data-disabled] .v-slider-track {\n    background: var(--vectis-color-surface-muted);\n  }\n\n  .v-slider[data-disabled] .v-slider-fill {\n    background: var(--vectis-color-text-subtle);\n  }\n\n  .v-slider[data-disabled] .v-slider-tick {\n    background: var(--vectis-color-text-subtle);\n  }\n\n  /* A tick sitting on the greyed fill takes the light colour back, so that it stays\n     visible against it — the same inversion VCheckbox applies to its disabled tick. */\n  .v-slider[data-disabled] .v-slider-tick[data-filled] {\n    background: var(--vectis-color-surface-muted);\n  }\n\n  .v-slider[data-disabled] .v-slider-labels {\n    color: var(--vectis-color-text-subtle);\n  }\n\n  .v-slider[data-disabled] .v-slider-input {\n    --slider-thumb-bg: var(--vectis-color-surface-muted);\n    --slider-thumb-border: var(--vectis-color-text-subtle);\n    --slider-thumb-shadow: none;\n    --slider-thumb-cursor: not-allowed;\n    cursor: not-allowed;\n  }\n\n  @media (prefers-reduced-motion: reduce) {\n    .v-slider-input {\n      --slider-thumb-transition: none;\n    }\n\n    .v-slider-tooltip {\n      transition: none;\n    }\n  }\n}\n</style>\n"],"mappings":""}
+{"version":3,"file":"VSlider.js","names":[],"sources":["../../../src/components/VSlider/VSlider.vue"],"sourcesContent":["<script setup lang=\"ts\">\n// @core\n/**\n * A value chosen by sliding a thumb along a track, optionally a range between two.\n *\n * Underneath is a native `<input type=\"range\">`, which brings the keyboard, the ARIA and the\n * form behaviour. The JS covers only what it cannot: keeping the pair of a range ordered —\n * there is no native two-thumb control, so a range is two superimposed — refusing a change\n * when `readonly`, which a range input has no native form of, feeding the optional number\n * fields, and computing the positions of the ticks and labels.\n *\n * Those positions reach the stylesheet as unitless inline fractions, and that is the whole\n * binding between the two. They matter because a thumb's CENTRE does not travel the full\n * width of the track: it runs from half a thumb in to half a thumb from the end, and\n * everything meant to line up with it has to follow that same run.\n */\n\nimport { computed, inject, ref, watch, watchEffect } from 'vue'\nimport VIcon from '../VIcon/VIcon.vue'\nimport { iconProps } from '../VIcon/iconProps'\nimport type { IconSource } from '../VIcon/types'\nimport VInput from '../VInput/VInput.vue'\nimport { inputGroupKey } from '../VInput/context'\n\nimport { useAriaLabel } from '../../composables/useAriaLabel'\nimport { useControlShape } from '../../composables/useControlShape'\nimport { useFieldIds } from '../../composables/useFieldIds'\nimport { useRootAttrs } from '../../composables/useRootAttrs'\nimport { isDev } from '../../utils/env'\nimport { clamp } from '../../utils/number'\nimport { useMessages } from '../../i18n/state'\n\n/**\n * What one step of the track is called: a piece of text, or an icon paired with the words\n * that name it, which is what a screen reader reads in place of the raw number.\n */\nexport type SliderLabel = string | { icon: IconSource; label: string }\n\n/** The value of a slider: one number, or an ordered pair of them in range mode. */\nexport type SliderValue = number | [number, number]\n\n/** Which way the track runs. */\nexport type SliderOrientation = 'horizontal' | 'vertical'\n\n/** The height of the number fields: 32, 40 or 48 pixels. */\nexport type SliderSize = 'sm' | 'md' | 'lg'\n\ninterface SliderProps {\n  /** The lowest value the thumb can reach. It is 0 by default. */\n  min?: number\n  /** The highest value the thumb can reach. It is 100 by default. */\n  max?: number\n  /**\n   * The gap between two values the thumb can stop on, 1 by default. It is also what the\n   * arrow keys move by, and what a value typed into the companion field is snapped to.\n   */\n  step?: number\n  /** Offers two thumbs to pick a range, which makes the v-model a pair of values. */\n  range?: boolean\n  /** Makes the slider unusable. */\n  disabled?: boolean\n  /**\n   * Shows the value without allowing it to be changed. The thumbs can still be focused and\n   * are announced as read-only, but neither the pointer nor the keyboard moves them, and the\n   * number fields turn read-only with them.\n   */\n  readonly?: boolean\n  /**\n   * Marks the value as invalid, which colours the thumbs and tells assistive technology\n   * so. It is for a rule the browser cannot check by itself.\n   */\n  invalid?: boolean\n  /**\n   * The height of the number fields `inputs` adds. Inside a VInputGroup the group's size\n   * wins, as it does for every field of the row.\n   */\n  size?: SliderSize\n  /**\n   * What screen readers announce for the slider. It is an accessible name and draws\n   * nothing on screen. In range mode the two thumbs are announced as the start and the\n   * end of it.\n   */\n  label?: string\n  /**\n   * A line of help under the track, stating what the numbers mean or where they may go. It\n   * is tied to the slider for assistive technology, so it is read out after the name rather\n   * than as part of it.\n   */\n  hint?: string\n  /** Turns the slider upright, with the lowest value at the bottom. */\n  orientation?: SliderOrientation\n  /**\n   * Adds a number field beside the slider for setting the value exactly: one, or one per\n   * end in range mode. Sliding is quick but imprecise; this is the way out.\n   */\n  inputs?: boolean\n  /**\n   * Marks each step on the track. Providing labels implies it. Past fifty steps the\n   * marks would be an unreadable comb and are not drawn at all.\n   */\n  ticks?: boolean\n  /**\n   * A label for every step, in order: a piece of text, or an icon with the words that\n   * name it for screen readers. They also become what a screen reader announces in\n   * place of the raw number.\n   */\n  labels?: SliderLabel[]\n  /** Shows the value in a bubble above the thumb while it is being moved or focused. */\n  tooltip?: boolean\n}\n\nconst props = withDefaults(defineProps<SliderProps>(), {\n  min: 0,\n  max: 100,\n  step: 1,\n  range: false,\n  disabled: false,\n  readonly: false,\n  invalid: false,\n  size: 'md',\n  label: undefined,\n  hint: undefined,\n  orientation: 'horizontal',\n  inputs: false,\n  ticks: false,\n  labels: undefined,\n  tooltip: false,\n})\n\n/**\n * The value: a single number, 0 to begin with, or an ordered pair once `range` is set. It\n * is that prop and not the shape of this value that decides how many thumbs are drawn.\n * The pair stays ordered whatever the reader does, a thumb taken past its sibling pushing\n * it along rather than stopping against it.\n */\nconst model = defineModel<SliderValue>({ default: 0 })\n\nconst emit = defineEmits<{\n  /**\n   * The value is BEING changed: every step of a drag, and every key that moves a thumb.\n   * It carries the whole value, a pair in range mode, and fires for either thumb. It is\n   * declared rather than left to fall through, because a range is two native controls and\n   * an attribute only ever reaches one of them.\n   */\n  input: [value: SliderValue]\n  /**\n   * The reader has SETTLED on a value: a thumb was released or moved by a key, or a number\n   * field was committed. It carries the whole value, a pair in range mode, and fires for\n   * either thumb, where the v-model follows every step of a drag.\n   */\n  change: [value: SliderValue]\n}>()\n\n// The number fields are fields of a VInputGroup row like any other, so the row's size and\n// its disabled state reach them through the same arbitration. A slider has no `compact` of\n// its own: only the row's can apply.\nconst group = inject(inputGroupKey, null)\nconst {\n  size: resolvedSize,\n  compact: resolvedCompact,\n  disabled: resolvedDisabled,\n} = useControlShape(\n  {\n    get size() {\n      return props.size\n    },\n    compact: false,\n    get disabled() {\n      return props.disabled\n    },\n  },\n  group,\n)\n\ntype Thumb = 'start' | 'end'\n\nconst startValue = computed(() => (Array.isArray(model.value) ? model.value[0] : props.min))\nconst endValue = computed(() =>\n  Array.isArray(model.value) ? model.value[1] : (model.value as number),\n)\n\nconst thumbValue = (which: Thumb) => (which === 'start' ? startValue.value : endValue.value)\n\n/**\n * Where a value sits along the run, as a fraction between 0 and 1. The guard covers a\n * slider whose two bounds are equal, which would otherwise divide by zero.\n */\nconst frac = (v: number) => clamp((v - props.min) / (props.max - props.min || 1), 0, 1)\n\n// @core — the ONE place a thumb is written, so what keeps the pair ordered exists once for\n// the thumbs and the number fields alike. A range is two native controls laid over one\n// another, and there is no dual-thumb control to inherit this behaviour from. It returns\n// what was written, which is what each caller reads back: a model that lags a parent\n// `v-model` would still hold the value from before.\n//\n// TRAP — the thumb being held PUSHES its sibling; it must not stop against it. Two thumbs\n// resting on the same value are one thumb as far as the pointer is concerned, the end one\n// being last in the DOM and therefore the only one it can reach — so a range stopped at\n// `[100, 100]` could only ever be raised, and at the maximum it could not move at all. The\n// pair stays ordered either way; what changes is which thumb gives way.\nfunction writeThumb(which: Thumb, n: number): SliderValue {\n  const next: SliderValue = !props.range\n    ? n\n    : which === 'start'\n      ? [n, Math.max(n, endValue.value)]\n      : [Math.min(n, startValue.value), n]\n  model.value = next\n  return next\n}\n\nconst writtenFor = (value: SliderValue, which: Thumb) =>\n  Array.isArray(value) ? value[which === 'start' ? 0 : 1] : value\n\nfunction onThumbInput(which: Thumb, event: Event) {\n  const el = event.target as HTMLInputElement\n  // @core\n  // A drag or a click on the track has ALREADY moved the native thumb when `input` fires,\n  // and the event cannot be cancelled: putting the value back is the only refusal there is.\n  // It lands before the browser paints, so the thumb never visibly leaves its place, and\n  // since the value at release is the one it started from, no `change` follows either.\n  if (props.readonly) {\n    el.value = String(thumbValue(which))\n    return\n  }\n  // Written back to the DOM as well: a thumb dragged past its sibling stops against it.\n  const next = writeThumb(which, Number(el.value))\n  el.value = String(writtenFor(next, which))\n  emit('input', next)\n}\n\n// @keyboard @core\n// The keys that move a range input, cancelled before the browser applies them when the\n// slider is read-only. Tab and every other key pass, so the thumbs stay reachable.\nconst VALUE_KEYS = new Set([\n  'ArrowUp',\n  'ArrowDown',\n  'ArrowLeft',\n  'ArrowRight',\n  'Home',\n  'End',\n  'PageUp',\n  'PageDown',\n])\n\nfunction onThumbKeydown(event: KeyboardEvent) {\n  if (props.readonly && VALUE_KEYS.has(event.key)) event.preventDefault()\n}\n\n// @core\n/*\n * A range is two native controls, and a consumer's `@change` could only ever reach ONE of\n * them through the forwarded attributes: moving the start thumb told nobody. So `change` is\n * declared and fed by both.\n *\n * TRAP — the settled value is read off the THUMB, never off the model. A key press fires\n * `input` and `change` back to back in one task, and under a parent `v-model` the model's\n * local copy only catches up when the parent re-renders, so it would still hold the value\n * from before the key.\n */\nfunction onThumbChange(which: Thumb, event: Event) {\n  if (props.readonly) return\n  const value = Number((event.target as HTMLInputElement).value)\n  if (!props.range) emit('change', value)\n  else if (which === 'start') emit('change', [value, Math.max(value, endValue.value)])\n  else emit('change', [Math.min(value, startValue.value), value])\n}\n\n/**\n * How many whole steps the thumb can actually stop on. It matters when the range does\n * not divide evenly by the step: the native control stops at the last step that fits,\n * short of the maximum, and the ticks have to agree with it.\n */\nconst stepCount = computed(() =>\n  props.step > 0 ? Math.floor((props.max - props.min) / props.step + 1e-9) : 0,\n)\n\n/**\n * The highest value a thumb can actually stop on, which is the last whole step and not\n * necessarily the maximum: with `min=0 max=95 step=10` the native control stops at 90.\n */\nconst lastStop = computed(() =>\n  props.step > 0 ? props.min + stepCount.value * props.step : props.max,\n)\n\nconst showTicks = computed(\n  () =>\n    (props.ticks || props.labels !== undefined) && stepCount.value >= 1 && stepCount.value <= 50,\n)\n\n/**\n * Each step's value and the style that places it, shared by the ticks and the labels. Only\n * the bounds and the step move them, so dragging a thumb rebuilds none of it: each style\n * object keeps its identity from one render to the next, and Vue skips a binding whose\n * object has not changed. Which ticks are FILLED does follow the value, and is asked\n * separately, in `isFilled`.\n */\nconst stepPlaces = computed(() => {\n  const length = Math.max(showTicks.value ? stepCount.value + 1 : 0, props.labels?.length ?? 0)\n  return Array.from({ length }, (_, i) => {\n    const value = props.min + i * props.step\n    return { value, style: { '--fill-fraction': String(frac(value)) } }\n  })\n})\n\nconst tickPlaces = computed(() =>\n  showTicks.value ? stepPlaces.value.slice(0, stepCount.value + 1) : [],\n)\n\nconst isFilled = (value: number) =>\n  props.range ? value >= startValue.value && value <= endValue.value : value <= endValue.value\n\n/** What a value is called, if the consumer named its step; failing that, the number itself. */\nfunction labelTextAt(value: number): string {\n  const item = props.labels?.[Math.round((value - props.min) / props.step)]\n  if (item === undefined) return String(value)\n  return typeof item === 'string' ? item : item.label\n}\n\n// @a11y\n/* What each thumb is announced as. There is no prop for the two halves: the wording\n   comes from the dictionary, which is also where it is changed.\n\n   With a single thumb there is nothing to distinguish: that thumb IS the value, so it\n   simply takes the resolved label, and is left unnamed when none was given. The\n   generic fallback applies to the NUMBER FIELD alone, which cannot go unnamed: a bare\n   field in a form has to say what it holds.\n\n   TRAP — the name has to be RESOLVED against the consumer's attributes rather than read\n   off the prop. The `:aria-label` below is bound AFTER the forwarded attributes, which is\n   what lets a range give its two thumbs distinct names; bound from a bare `props.label`\n   it ALSO overwrote an `aria-label` the consumer had written, with `undefined`, and\n   `mergeProps` copies the key all the same. `useAriaLabel` is that resolution: it hands\n   back the consumer's own name when there is one, and nothing at all under an\n   `aria-labelledby`, which names the thumb by itself. */\nconst m = useMessages()\nconst resolvedLabel = useAriaLabel(() => props.label)\nconst startLabel = computed(() =>\n  resolvedLabel.value ? m.value.slider.rangeStart(resolvedLabel.value) : m.value.slider.start,\n)\nconst endLabel = computed(() =>\n  resolvedLabel.value ? m.value.slider.rangeEnd(resolvedLabel.value) : m.value.slider.end,\n)\nconst thumbEndLabel = computed(() => (props.range ? endLabel.value : resolvedLabel.value))\nconst fieldEndLabel = computed(() =>\n  props.range ? endLabel.value : (resolvedLabel.value ?? m.value.slider.value),\n)\n\nconst startValueText = computed(() =>\n  props.range && props.labels ? labelTextAt(startValue.value) : undefined,\n)\nconst endValueText = computed(() => (props.labels ? labelTextAt(endValue.value) : undefined))\n\n// @a11y\n/*\n * The wrapper-root split. The root here is a layout box holding the labels, the track and\n * the optional number fields, so a consumer's `name`, `id`, `required` and `aria-*` have\n * to be redirected onto the real `<input type=\"range\">` — left on the wrapper, a `name`\n * submits nothing and a `<label for>` points at a div.\n *\n * They go to the END thumb, which is the one always rendered. A RANGE has two thumbs and\n * therefore no single value to submit, which the warning below says out loud rather than\n * letting a form come back with half the answer.\n */\ndefineOptions({ inheritAttrs: false })\nconst { attrs, rootClass, rootStyle, forwardedAttrs } = useRootAttrs()\n\n// The hint is APPENDED to whatever the consumer already pointed at rather than replacing\n// it, which is why the binding below sits after the forwarded attributes, as on every\n// other field of the design system.\nconst { hintId, describedBy } = useFieldIds(attrs, () => !!props.hint)\n\n// @devwarn\n/*\n * Every guard here describes something that fails SILENTLY. They sit in an effect, so a\n * bound that only becomes wrong on a later render is still caught, and each sentence is\n * given once per instance: the same warning repeated on every keystroke is how a warning\n * stops being read (the `useFileField` arrangement).\n */\nif (isDev) {\n  // Keyed by a short id rather than by the sentence: each of these embeds a count, so the\n  // same guard reported twice would read as two different messages and warn again.\n  const warned = new Set<string>()\n  const warn = (id: string, message: string) => {\n    if (warned.has(id)) return\n    warned.add(id)\n    console.warn(`[VSlider] ${message}`)\n  }\n  watchEffect(() => {\n    if (props.step <= 0)\n      warn(\n        'step',\n        `step=\"${props.step}\" cannot move a thumb: the arrow keys do nothing and a value typed into a field is committed as it stands. Give a positive step.`,\n      )\n    if ((props.ticks || props.labels) && stepCount.value > 50)\n      warn(\n        'ticks',\n        `${stepCount.value} steps: no tick is drawn past 50, the comb being unreadable.`,\n      )\n    if (props.labels && props.labels.length !== stepCount.value + 1)\n      warn(\n        'labels',\n        `${props.labels.length} labels for ${stepCount.value + 1} steps: one label per step expected.`,\n      )\n    if (props.range && attrs.name !== undefined)\n      warn(\n        'name',\n        `name=\"${String(attrs.name)}\" on a range: only the end thumb carries it, so the form receives one value of the two. Bind the model to two inputs of your own instead.`,\n      )\n  })\n}\n\n// @core\n// The text held by the number fields, kept apart from the slider's own value.\n//\n// It is typed as text OR a number because these are number fields, whose value Vue\n// converts to a number as soon as it can be read as one — while an empty field, or one\n// holding a half-typed \"1-\", stays text. That is why the value is turned back into text\n// when it is committed. The start field exists in range mode only, and so does its sync.\nconst startFieldText = ref<string | number>(String(startValue.value))\nconst endFieldText = ref<string | number>(String(endValue.value))\n\n// Sliding the thumb keeps the fields in step, continuously.\nwatch(startValue, (v) => {\n  if (props.range) startFieldText.value = String(v)\n})\nwatch(endValue, (v) => (endFieldText.value = String(v)))\n\n// @core\n/**\n * Takes what was typed in a field and makes it the value — but only once the reader has\n * finished, on leaving the field or on Enter. Reading it as they type would clamp the\n * \"1\" of \"15\" to the minimum before the 5 was ever pressed.\n *\n * Anything unreadable, an empty field included, silently puts the previous value back.\n */\nfunction commitField(which: Thumb) {\n  const raw = which === 'start' ? startFieldText.value : endFieldText.value\n  // TRAP — parsed rather than converted: an empty string parses to nothing, which is\n  // what triggers the revert below, where converting it would give ZERO and quietly\n  // overwrite the value with it.\n  const parsed = Number.parseFloat(String(raw))\n  if (Number.isNaN(parsed)) {\n    resyncFields()\n    return\n  }\n  // Brought onto the nearest step. The rounding that follows removes the noise decimal\n  // steps leave behind — a tenth cannot be represented exactly, so 0.1 × 3 comes out as\n  // 0.30000000000000004.\n  //\n  // TRAP — the ceiling is the last step that FITS, never `max` itself. A native range\n  // stops there (that is what `stepCount` counts), so clipped to a `max` the step does not\n  // reach, the model held a value the thumb could not: the browser sanitized its input back\n  // down, and the number, the thumb and the fill then said three different things. A step\n  // that cannot move anything leaves the clamped value alone rather than dividing by it.\n  const clamped = clamp(parsed, props.min, props.max)\n  const snapped =\n    props.step > 0\n      ? props.min + Math.round((clamped - props.min) / props.step) * props.step\n      : clamped\n  const value = Math.min(lastStop.value, Math.round(snapped * 1e10) / 1e10)\n  const previous = thumbValue(which)\n  const next = writeThumb(which, value)\n  // Emitted only when the value MOVED, as a native range emits nothing for a key that\n  // cannot move its thumb — and the payload is `next`, the model's local copy lagging a\n  // parent `v-model` (see `onThumbChange`).\n  if (writtenFor(next, which) !== previous) emit('change', next)\n  // Put back explicitly, because a commit that does not change the value — typing 200\n  // where the maximum is 100 — changes nothing for the watchers to react to, and the\n  // field would go on showing what was typed.\n  resyncFields()\n}\n\nfunction resyncFields() {\n  if (props.range) startFieldText.value = String(startValue.value)\n  endFieldText.value = String(endValue.value)\n}\n\nconst endThumbEl = ref<HTMLInputElement | null>(null)\n\n// The root is a layout box, so a template ref on the component reaches the wrapper and not\n// the control. Both members point at the END thumb: it is the one always rendered, and the\n// one the consumer's `id` lands on, so `focus()` goes where a `<label for>` would send it.\ndefineExpose({\n  /** Moves the focus to the end thumb, the only thumb outside range mode. */\n  focus: (options?: FocusOptions) => endThumbEl.value?.focus(options),\n  /** The end thumb's real `<input type=\"range\">`, for what `focus` does not cover. */\n  el: endThumbEl,\n})\n</script>\n\n<template>\n  <div\n    class=\"v-slider\"\n    :class=\"rootClass\"\n    :data-range=\"range ? '' : undefined\"\n    :data-disabled=\"resolvedDisabled ? '' : undefined\"\n    :data-readonly=\"readonly ? '' : undefined\"\n    :data-invalid=\"invalid ? '' : undefined\"\n    :data-size=\"resolvedSize\"\n    :data-orientation=\"orientation\"\n    :style=\"[\n      rootStyle,\n      {\n        '--slider-start-fraction': range ? String(frac(startValue)) : undefined,\n        '--slider-end-fraction': String(frac(endValue)),\n      },\n    ]\"\n  >\n    <VInput\n      v-if=\"inputs && range\"\n      v-model=\"startFieldText\"\n      class=\"v-slider-field v-slider-field-start\"\n      type=\"number\"\n      :size=\"resolvedSize\"\n      :compact=\"resolvedCompact\"\n      :min=\"min\"\n      :max=\"max\"\n      :step=\"step\"\n      :disabled=\"resolvedDisabled\"\n      :readonly=\"readonly\"\n      :invalid=\"invalid\"\n      :aria-label=\"startLabel\"\n      @change=\"commitField('start')\"\n    />\n    <div class=\"v-slider-rail\">\n      <span class=\"v-slider-control\">\n        <span class=\"v-slider-track\" aria-hidden=\"true\">\n          <span class=\"v-slider-fill\" />\n          <span\n            v-for=\"(tick, i) in tickPlaces\"\n            :key=\"i\"\n            class=\"v-slider-tick\"\n            :data-filled=\"isFilled(tick.value) ? '' : undefined\"\n            :style=\"tick.style\"\n          />\n        </span>\n        <input\n          v-if=\"range\"\n          type=\"range\"\n          class=\"v-slider-input v-slider-input-start\"\n          :min=\"min\"\n          :max=\"max\"\n          :step=\"step\"\n          :disabled=\"resolvedDisabled\"\n          :value=\"startValue\"\n          :aria-label=\"startLabel\"\n          :aria-valuetext=\"startValueText\"\n          :aria-invalid=\"invalid || undefined\"\n          :aria-readonly=\"readonly || undefined\"\n          @keydown=\"onThumbKeydown\"\n          @input=\"onThumbInput('start', $event)\"\n          @change=\"onThumbChange('start', $event)\"\n        />\n        <!-- The consumer's attributes come FIRST, so what the component decides for\n             itself — the bounds, the value and the disabled state — cannot be\n             overwritten by one of them, and so that an ARIA state the consumer sets is\n             not erased by an `undefined` of ours. `aria-valuetext` is one of those: the\n             component has one to say only when `labels` was given.\n\n             The accessible NAME is the exception, and it is bound after on purpose: a\n             range has two thumbs and needs a distinct word for each. It reads a name\n             already resolved against these same attributes, so nothing is lost. -->\n        <input\n          ref=\"endThumbEl\"\n          :aria-invalid=\"invalid || undefined\"\n          :aria-readonly=\"readonly || undefined\"\n          :aria-valuetext=\"endValueText\"\n          v-bind=\"forwardedAttrs\"\n          type=\"range\"\n          class=\"v-slider-input v-slider-input-end\"\n          :min=\"min\"\n          :max=\"max\"\n          :step=\"step\"\n          :disabled=\"resolvedDisabled\"\n          :value=\"endValue\"\n          :aria-label=\"thumbEndLabel\"\n          :aria-describedby=\"describedBy\"\n          @keydown=\"onThumbKeydown\"\n          @input=\"onThumbInput('end', $event)\"\n          @change=\"onThumbChange('end', $event)\"\n        />\n      </span>\n      <span\n        v-if=\"tooltip && range\"\n        class=\"v-slider-tooltip v-slider-tooltip-start\"\n        aria-hidden=\"true\"\n      >\n        <span class=\"v-slider-tooltip-bubble\">{{ startValueText ?? startValue }}</span>\n      </span>\n      <span v-if=\"tooltip\" class=\"v-slider-tooltip v-slider-tooltip-end\" aria-hidden=\"true\">\n        <span class=\"v-slider-tooltip-bubble\">{{ endValueText ?? endValue }}</span>\n      </span>\n    </div>\n    <div v-if=\"labels\" class=\"v-slider-labels\">\n      <span\n        v-for=\"(item, i) in labels\"\n        :key=\"i\"\n        class=\"v-slider-label\"\n        :style=\"stepPlaces[i]?.style\"\n      >\n        <template v-if=\"typeof item === 'string'\">{{ item }}</template>\n        <VIcon v-else v-bind=\"iconProps(item.icon)\" :label=\"item.label\" />\n      </span>\n    </div>\n    <VInput\n      v-if=\"inputs\"\n      v-model=\"endFieldText\"\n      class=\"v-slider-field v-slider-field-end\"\n      type=\"number\"\n      :size=\"resolvedSize\"\n      :compact=\"resolvedCompact\"\n      :min=\"min\"\n      :max=\"max\"\n      :step=\"step\"\n      :disabled=\"resolvedDisabled\"\n      :readonly=\"readonly\"\n      :invalid=\"invalid\"\n      :aria-label=\"fieldEndLabel\"\n      @change=\"commitField('end')\"\n    />\n    <span v-if=\"hint\" :id=\"hintId\" class=\"v-slider-hint\">{{ hint }}</span>\n  </div>\n</template>\n\n<style>\n@layer vectis.components {\n  .v-slider {\n    --slider-thumb: var(--vectis-control-size-slider-thumb);\n    --slider-track: var(--vectis-control-size-slider-track);\n    display: grid;\n    grid-template-areas: 'rail';\n    grid-template-columns: minmax(0, 1fr);\n    align-items: center;\n    column-gap: var(--vectis-space-2);\n    row-gap: var(--vectis-space-1);\n    inline-size: 100%;\n    font-family: var(--vectis-text-family);\n  }\n\n  /*\n     The zones the root lays out, from least to most furnished. `:has()` takes the\n     specificity of its argument, so the single-condition rules are all (0,2,0) and the\n     two-condition ones (0,3,0) — which means the five below are arbitrated by SOURCE\n     ORDER as much as by weight, and a range slider with inputs matches three of them at\n     once. They must stay in this order, each configuration overwriting the poorer one it\n     builds on. Alphabetize them, or move `field-start` above `field-end`, and the start\n     field lands outside the grid: no error, just a control sitting where nothing put it. */\n  .v-slider:has(.v-slider-labels) {\n    grid-template-areas: 'rail' 'labels';\n  }\n\n  .v-slider:has(.v-slider-field-end) {\n    grid-template-areas: 'rail field-end';\n    grid-template-columns: minmax(0, 1fr) auto;\n  }\n\n  .v-slider:has(.v-slider-field-end):has(.v-slider-labels) {\n    grid-template-areas: 'rail field-end' 'labels .';\n  }\n\n  .v-slider:has(.v-slider-field-start) {\n    grid-template-areas: 'field-start rail field-end';\n    grid-template-columns: auto minmax(0, 1fr) auto;\n  }\n\n  .v-slider:has(.v-slider-field-start):has(.v-slider-labels) {\n    grid-template-areas: 'field-start rail field-end' '. labels .';\n  }\n\n  .v-slider-rail {\n    grid-area: rail;\n    position: relative;\n    block-size: var(--slider-thumb);\n  }\n\n  .v-slider-control {\n    position: absolute;\n    inset: 0;\n  }\n\n  .v-slider-track {\n    position: absolute;\n    inset-inline: 0;\n    inset-block: 0;\n    margin-block: auto;\n    block-size: var(--slider-track);\n    border-radius: var(--vectis-radius-pill);\n    background: var(--vectis-color-border);\n    overflow: hidden;\n  }\n\n  /*\n     Where a thumb's CENTRE sits for the fraction `--fill-fraction`, written once for every\n     element lined up with it: half a thumb in, then the fraction of the run that is left.\n\n     TRAP — it must be declared on the element that CARRIES the fraction, never on an\n     ancestor. A custom property's `var()` is resolved where the property is declared, so\n     set on the root it would read a `--fill-fraction` the root does not have and turn\n     invalid, and every tick, label and bubble would drop to its static position at the\n     start of the track, with no error. The `100%`, on the other hand, stays a percentage\n     until it is used, and resolves against the box of the property that reads it — the\n     inline size of the track for an inset, the block size in the vertical rules. */\n  .v-slider-fill,\n  .v-slider-tick,\n  .v-slider-tooltip,\n  .v-slider-label {\n    --slider-at: calc(\n      var(--slider-thumb) / 2 + (100% - var(--slider-thumb)) * var(--fill-fraction)\n    );\n  }\n\n  .v-slider-fill {\n    --fill-fraction: var(--slider-end-fraction);\n    position: absolute;\n    inset-block: 0;\n    inset-inline-start: 0;\n    inline-size: var(--slider-at);\n    background: var(--vectis-color-accent);\n  }\n\n  .v-slider[data-range] .v-slider-fill {\n    --fill-fraction: var(--slider-start-fraction);\n    inset-inline-start: var(--slider-at);\n    inline-size: calc(\n      (100% - var(--slider-thumb)) * (var(--slider-end-fraction) - var(--slider-start-fraction))\n    );\n  }\n\n  .v-slider-tick {\n    --slider-tick: calc(var(--slider-track) / 3 * 2);\n    position: absolute;\n    inset-block: 0;\n    margin-block: auto;\n    inset-inline-start: calc(var(--slider-at) - var(--slider-tick) / 2);\n    inline-size: var(--slider-tick);\n    block-size: var(--slider-tick);\n    border-radius: var(--vectis-radius-pill);\n    background: var(--vectis-color-border-strong);\n  }\n\n  .v-slider-tick[data-filled] {\n    background: var(--vectis-color-text-on-accent);\n  }\n\n  /* The two controls lie exactly on top of one another, so only their thumbs are allowed\n     to receive the pointer. Without that, the one on top would swallow every click and\n     the other thumb could never be grabbed.\n\n     The thumb's paint lives in variables set HERE, on the control, and read once by each\n     vendor pseudo-element below. That is what lets every state be written a single time:\n     a state pseudo-class written after the thumb's own pseudo-element is unreliable across\n     browsers, so a state has to be read on the control either way, and the thumb inherits\n     the variables from it.\n\n     The thumb is white in BOTH themes, the VSwitch thumb's colour: on a dark page a thumb\n     painted in `surface` sinks into the track instead of standing out as the handle. */\n  .v-slider-input {\n    --slider-thumb-bg: var(--vectis-color-text-on-accent);\n    --slider-thumb-border: var(--vectis-color-accent);\n    --slider-thumb-shadow: var(--vectis-shadow-xs);\n    --slider-thumb-outline: none;\n    --slider-thumb-cursor: pointer;\n    --slider-thumb-transition: background-color var(--vectis-duration-fast)\n      var(--vectis-ease-default);\n    position: absolute;\n    inset: 0;\n    width: 100%;\n    height: 100%;\n    margin: 0;\n    appearance: none;\n    background: transparent;\n    pointer-events: none;\n  }\n\n  /* With a single thumb there is nothing underneath to protect, so the whole control\n     takes the pointer again — which is what makes clicking the track jump the value\n     there and start dragging at once, natively and with no code at all. The accepted\n     side effect is that the thumb lights up when the pointer is anywhere over the\n     track. */\n  .v-slider:not([data-range]) .v-slider-input {\n    pointer-events: auto;\n    cursor: pointer;\n  }\n\n  /* TRAP — the two vendor pseudo-elements stay in two separate rules. A selector list\n     holding one a browser does not know is dropped WHOLE, so merged, each engine would\n     throw away the other's thumb and draw its native one. */\n  .v-slider-input::-webkit-slider-thumb {\n    appearance: none;\n    pointer-events: auto;\n    width: var(--slider-thumb);\n    height: var(--slider-thumb);\n    border-radius: var(--vectis-radius-pill);\n    background: var(--slider-thumb-bg);\n    border: var(--vectis-control-border-width) solid var(--slider-thumb-border);\n    box-shadow: var(--slider-thumb-shadow);\n    outline: var(--slider-thumb-outline);\n    outline-offset: var(--vectis-focus-ring-offset);\n    cursor: var(--slider-thumb-cursor);\n    transition: var(--slider-thumb-transition);\n  }\n\n  .v-slider-input::-moz-range-thumb {\n    pointer-events: auto;\n    width: var(--slider-thumb);\n    height: var(--slider-thumb);\n    border-radius: var(--vectis-radius-pill);\n    background: var(--slider-thumb-bg);\n    border: var(--vectis-control-border-width) solid var(--slider-thumb-border);\n    box-shadow: var(--slider-thumb-shadow);\n    outline: var(--slider-thumb-outline);\n    outline-offset: var(--vectis-focus-ring-offset);\n    cursor: var(--slider-thumb-cursor);\n    transition: var(--slider-thumb-transition);\n  }\n\n  /* The states, all at (0,3,0) but the base, so their ORDER arbitrates them: hover, then\n     read-only, invalid and disabled, each overriding what came before on a thumb that is\n     several at once.\n\n     The hover tint is mixed from the thumb's own white rather than read from\n     `accent-surface`: that token turns dark in the dark theme, and a white thumb would\n     flash nearly black under the pointer. */\n  .v-slider-input:is(:hover, :active):not(:disabled) {\n    --slider-thumb-bg: color-mix(\n      in oklab,\n      var(--vectis-color-text-on-accent),\n      var(--vectis-color-accent) 10%\n    );\n  }\n\n  .v-slider-input:focus-visible {\n    --slider-thumb-outline: var(--vectis-focus-ring-width) solid var(--vectis-focus-ring-color);\n    outline: none;\n  }\n\n  /* The muted text colour a read-only VCheckbox takes, on the fill and the thumb's ring:\n     the value stays plainly readable, the accent no longer invites a drag. */\n  .v-slider[data-readonly] .v-slider-input {\n    --slider-thumb-bg: var(--vectis-color-surface);\n    --slider-thumb-border: var(--vectis-color-text-muted);\n    --slider-thumb-cursor: default;\n    cursor: default;\n  }\n\n  .v-slider[data-readonly] .v-slider-fill {\n    background: var(--vectis-color-text-muted);\n  }\n\n  .v-slider[data-readonly] .v-slider-tick[data-filled] {\n    background: var(--vectis-color-surface);\n  }\n\n  /* The border colour VCheckbox and VRadio take when invalid, on the thumb's ring. */\n  .v-slider[data-invalid] .v-slider-input {\n    --slider-thumb-border: var(--vectis-color-danger);\n  }\n\n  /* The bubble showing the value. It looks like a VTooltip but is placed by arithmetic\n     rather than anchored to the thumb: a native thumb is a pseudo-element, and the\n     browser's anchoring cannot attach anything to one. The fraction it follows is the one\n     the root already carries for the fill. */\n  .v-slider-tooltip {\n    position: absolute;\n    inset-block-end: calc(100% + var(--vectis-space-2));\n    inset-inline-start: var(--slider-at);\n    inline-size: 0;\n    display: flex;\n    justify-content: center;\n    opacity: 0;\n    visibility: hidden;\n    transition:\n      opacity var(--vectis-duration-fast) var(--vectis-ease-default),\n      visibility var(--vectis-duration-fast) var(--vectis-ease-default);\n  }\n\n  .v-slider-tooltip-start {\n    --fill-fraction: var(--slider-start-fraction);\n  }\n\n  .v-slider-tooltip-end {\n    --fill-fraction: var(--slider-end-fraction);\n  }\n\n  .v-slider:has(.v-slider-input-start:active) .v-slider-tooltip-start,\n  .v-slider:has(.v-slider-input-start:focus-visible) .v-slider-tooltip-start,\n  .v-slider:has(.v-slider-input-end:active) .v-slider-tooltip-end,\n  .v-slider:has(.v-slider-input-end:focus-visible) .v-slider-tooltip-end {\n    opacity: 1;\n    visibility: visible;\n  }\n\n  .v-slider-tooltip-bubble {\n    padding: var(--vectis-space-1) var(--vectis-space-2);\n    background: var(--vectis-color-surface-inverse);\n    color: var(--vectis-color-text-on-inverse);\n    font-size: var(--vectis-text-caption-size);\n    line-height: var(--vectis-text-caption-leading);\n    /* VTooltip's bubble corner, so the two tooltips of the design system stay one shape. */\n    border-radius: min(var(--vectis-radius-interactive), calc(0.5lh + var(--vectis-space-1)));\n    box-shadow: var(--vectis-shadow-sm);\n    white-space: nowrap;\n  }\n\n  .v-slider-labels {\n    grid-area: labels;\n    position: relative;\n    /* The labels are positioned individually and therefore contribute no height of\n       their own; this reserves enough room for either kind, a small line of text or an\n       icon. */\n    min-block-size: var(--vectis-icon-size-md);\n    /* The pair travels together, as it does in every `[data-size]` block of\n       control-size.css: the size applies to every source, the optical size only to the\n       ligature, and setting one without the other draws a 20px glyph cut for 24. */\n    --vectis-icon-size: var(--vectis-icon-size-md);\n    --vectis-icon-opsz: 20;\n    font-size: var(--vectis-text-caption-size);\n    color: var(--vectis-color-text-muted);\n  }\n\n  /* A box of zero width placed exactly on the step: its content then overflows equally\n     on both sides, which centres it there. Centring it with a transform would be the\n     usual trick, but a transform is physical and would have to be undone for the\n     vertical orientation and again for a right-to-left page. */\n  .v-slider-label {\n    position: absolute;\n    inset-block-start: 0;\n    inset-inline-start: var(--slider-at);\n    inline-size: 0;\n    display: flex;\n    justify-content: center;\n    white-space: nowrap;\n  }\n\n  /* The hint takes no area of its own: it spans every column and is AUTO-PLACED, which\n     drops it into an implicit row under whichever of the eleven zone templates is in force.\n     Given a row in each of them instead, the `row-gap` would open under every slider that\n     has no hint at all. */\n  .v-slider-hint {\n    grid-column: 1 / -1;\n    font-size: var(--vectis-text-caption-size);\n    line-height: var(--vectis-text-caption-leading);\n    color: var(--vectis-color-text-muted);\n  }\n\n  .v-slider[data-disabled] .v-slider-hint {\n    color: var(--vectis-color-text-subtle);\n  }\n\n  .v-slider-field.v-input {\n    inline-size: var(--vectis-control-size-slider-field);\n  }\n\n  /* Compounded with `.v-input` for the same reason as the width above: these land on an\n     element VInput's own sheet styles, and at (0,1,0) they would TIE with `.v-input`. They\n     set a `grid-area`, which VInput does not, so nothing is wrong today; the point is that\n     one of the three rules on this element was hardened and two were not. */\n  .v-slider-field-start.v-input {\n    grid-area: field-start;\n  }\n\n  .v-slider-field-end.v-input {\n    grid-area: field-end;\n  }\n\n  .v-slider[data-orientation='vertical'] {\n    grid-template-areas: 'rail';\n    grid-template-columns: none;\n    inline-size: fit-content;\n    justify-items: center;\n  }\n\n  .v-slider[data-orientation='vertical']:has(.v-slider-labels) {\n    grid-template-areas: 'rail labels';\n    grid-template-columns: auto auto;\n  }\n\n  .v-slider[data-orientation='vertical']:has(.v-slider-field-end) {\n    grid-template-areas: 'field-end' 'rail';\n    grid-template-columns: none;\n  }\n\n  .v-slider[data-orientation='vertical']:has(.v-slider-field-end):has(.v-slider-labels) {\n    grid-template-areas: 'field-end .' 'rail labels';\n    grid-template-columns: auto auto;\n  }\n\n  .v-slider[data-orientation='vertical']:has(.v-slider-field-start) {\n    grid-template-areas: 'field-end' 'rail' 'field-start';\n    grid-template-columns: none;\n  }\n\n  .v-slider[data-orientation='vertical']:has(.v-slider-field-start):has(.v-slider-labels) {\n    grid-template-areas: 'field-end .' 'rail labels' 'field-start .';\n    grid-template-columns: auto auto;\n  }\n\n  .v-slider[data-orientation='vertical'] .v-slider-rail {\n    inline-size: var(--slider-thumb);\n    block-size: var(--vectis-control-size-slider-length);\n  }\n\n  /* Only this inner box is turned upright, and that is the whole trick: the track, the\n     fill and the ticks are all placed with logical properties, so they follow the change\n     of axis with no rule written a second time — while the bubbles and the labels stay\n     outside that box, and therefore keep their text horizontal.\n\n     The direction is reversed with it so that the lowest value ends up at the bottom. */\n  .v-slider[data-orientation='vertical'] .v-slider-control {\n    writing-mode: vertical-lr;\n    direction: rtl;\n  }\n\n  .v-slider[data-orientation='vertical'] .v-slider-tooltip {\n    inset-block-end: var(--slider-at);\n    inset-inline-start: auto;\n    inset-inline-end: calc(100% + var(--vectis-space-2));\n    inline-size: auto;\n    block-size: 0;\n    align-items: center;\n    justify-content: flex-end;\n  }\n\n  .v-slider[data-orientation='vertical'] .v-slider-labels {\n    align-self: stretch;\n    min-block-size: auto;\n  }\n\n  .v-slider[data-orientation='vertical'] .v-slider-label {\n    inset-block-start: auto;\n    inset-block-end: var(--slider-at);\n    inset-inline-start: 0;\n    inline-size: auto;\n    block-size: 0;\n    align-items: center;\n    justify-content: flex-start;\n  }\n\n  /* A disabled slider greys out through the colour tokens, the same ones VCheckbox and\n     VSwitch use, and never through opacity. It comes LAST among the states, so a slider\n     both disabled and read-only or invalid is drawn disabled. */\n  .v-slider[data-disabled] {\n    cursor: not-allowed;\n  }\n\n  .v-slider[data-disabled] .v-slider-track {\n    background: var(--vectis-color-surface-muted);\n  }\n\n  .v-slider[data-disabled] .v-slider-fill {\n    background: var(--vectis-color-text-subtle);\n  }\n\n  .v-slider[data-disabled] .v-slider-tick {\n    background: var(--vectis-color-text-subtle);\n  }\n\n  /* A tick sitting on the greyed fill takes the light colour back, so that it stays\n     visible against it — the same inversion VCheckbox applies to its disabled tick. */\n  .v-slider[data-disabled] .v-slider-tick[data-filled] {\n    background: var(--vectis-color-surface-muted);\n  }\n\n  .v-slider[data-disabled] .v-slider-labels {\n    color: var(--vectis-color-text-subtle);\n  }\n\n  .v-slider[data-disabled] .v-slider-input {\n    --slider-thumb-bg: var(--vectis-color-surface-muted);\n    --slider-thumb-border: var(--vectis-color-text-subtle);\n    --slider-thumb-shadow: none;\n    --slider-thumb-cursor: not-allowed;\n    cursor: not-allowed;\n  }\n\n  /* Windows forced colors erase every author colour, and the slider is painted almost\n     entirely in backgrounds: the track, the fill and the ticks all flatten to `Canvas` and\n     the bar disappears, leaving a thumb whose border is the only thing left on screen. The\n     track draws its own edge as an inset ring here, the fill takes the system Highlight\n     pair the rest of the design system uses for a selected state, and the ticks fall back\n     to the text colour, inverted over the fill the way they already are over the accent.\n\n     (0,4,0) is enough: nothing in this sheet reaches past (0,3,0). */\n  @media (forced-colors: active) {\n    .v-slider .v-slider-track {\n      forced-color-adjust: none;\n      background: Canvas;\n      box-shadow: inset 0 0 0 var(--vectis-control-border-width) CanvasText;\n    }\n\n    .v-slider .v-slider-fill {\n      forced-color-adjust: none;\n      background: Highlight;\n    }\n\n    .v-slider .v-slider-tick {\n      forced-color-adjust: none;\n      background: CanvasText;\n    }\n\n    .v-slider .v-slider-tick[data-filled] {\n      background: HighlightText;\n    }\n\n    .v-slider .v-slider-input {\n      forced-color-adjust: none;\n      --slider-thumb-bg: Canvas;\n      --slider-thumb-border: CanvasText;\n      --slider-thumb-shadow: none;\n    }\n\n    .v-slider[data-disabled] .v-slider-track {\n      box-shadow: inset 0 0 0 var(--vectis-control-border-width) GrayText;\n    }\n\n    .v-slider[data-disabled] .v-slider-fill,\n    .v-slider[data-disabled] .v-slider-tick {\n      background: GrayText;\n    }\n\n    .v-slider[data-disabled] .v-slider-input {\n      --slider-thumb-border: GrayText;\n    }\n  }\n\n  @media (prefers-reduced-motion: reduce) {\n    .v-slider-input {\n      --slider-thumb-transition: none;\n    }\n\n    .v-slider-tooltip {\n      transition: none;\n    }\n  }\n}\n</style>\n"],"mappings":""}