[{"data":1,"prerenderedAt":934},["ShallowReactive",2],{"cmdk-index":3,"content:\u002Fguides\u002Frtl":260},[4,8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156,160,164,168,172,176,180,184,188,192,196,200,204,208,212,216,220,224,228,232,236,240,244,248,252,256],{"path":5,"title":6,"description":7},"\u002Fcomponents\u002Faccordion","Accordion","A disclosure list built entirely on native \u003Cdetails>\u002F\u003Csummary> elements — zero JavaScript, zero\nARIA reinvention. The browser supplies the disclosure role, aria-expanded, Enter\u002FSpace toggling,\nfocus, and find-in-page expansion for free. Single-open (exclusive) mode uses the platform\nexclusive-accordion feature (Baseline 2024): every \u003Cdetails> shares one auto-generated name, so\nthe browser closes siblings when one opens. multiple drops the shared name so each item opens\nindependently.",{"path":9,"title":10,"description":11},"\u002Fcomponents\u002Falert","Alert","A styled, accessible notification banner. Its live-region politeness is derived from the color —\nurgent danger \u002F warning render role=\"alert\" (assertive), everything else role=\"status\" (polite) —\nso a non-urgent banner isn't announced assertively (override with the live prop). It supports an\noptional icon, a title, body text, an actions row, and a dismiss button.",{"path":13,"title":14,"description":15},"\u002Fcomponents\u002Favatar","Avatar","A data-display component that shows an image, or initials derived from name when there is no\nimage (or while it loads). Supports a title \u002F subtitle column for list and profile UIs.",{"path":17,"title":18,"description":19},"\u002Fcomponents\u002Fbadge","Badge","A small status or count indicator. Attach it to any element as a floating pip, drop it inline next\nto text, or render it standalone — all three modes share the same class surface.",{"path":21,"title":22,"description":23},"\u002Fcomponents\u002Fbutton","Button","A styled, accessible button. Dynamic state is expressed through real attributes — disabled becomes\na true disabled (or aria-disabled for link buttons), loading sets aria-busy, and it ships a\nvisible :focus-visible ring.",{"path":25,"title":26,"description":27},"\u002Fcomponents\u002Fcard","Card","A surface container for grouping related content — a header (prepend slot · title · subtitle ·\nappend slot), a body, and optional action rows. It is the most composed styled component, yet the\nstandalone markup is just nested .ori-card__* elements, so it works without Vue.",{"path":29,"title":30,"description":31},"\u002Fcomponents\u002Fcheckbox","Checkbox","A styled, accessible checkbox built on a real \u003Cinput type=\"checkbox\"> — kept in the DOM\n(visually hidden over a custom box) so keyboard, focus, and native form submission work for free.\nThe accent color and :focus-visible ring are driven by the ori-color token; invalid sets\naria-invalid; disabled is the native attribute.",{"path":33,"title":34,"description":35},"\u002Fcomponents\u002Fcolor-picker","Color picker","An accessible color picker: a 2D saturation × brightness area, a hue slider, a hex field, and\noptional preset swatches — an inline panel you compose into an OriPopover for a\nswatch-triggered flow. Behavior lives in the framework-agnostic useColorPicker (a zero-dependency sRGB +\n2D-area engine, no adapter or machine); the styled component reuses OriSlider for the\nhue channel and OriInput for the hex field. v-model carries a lowercase color\nstring; the internal working model is HSVA, so the hue survives when you drag into a corner and back.",{"path":37,"title":38,"description":39},"\u002Fcomponents\u002Fcombobox","Combobox","A filterable single-select listbox — type to filter, navigate with the keyboard, pick one. It is the\nfirst component driven end-to-end by @oriui\u002Fheadless: the state machine + prop-getters own the\nbehavior (open\u002Fclose, filtering, the active-descendant highlight, selection, and the full\nWAI-ARIA keyboard), and OriCombobox renders the styled shell on top. Unlike the pure-CSS\ncomponents, the behavior needs JavaScript — the standalone classes give you the look, and\nuseCombobox gives you the behavior for any UI.",{"path":41,"title":42,"description":43},"\u002Fcomponents\u002Fdialog","Dialog","A modal dialog — the library's first genuinely interactive component, built on the native\n\u003Cdialog> element. Unlike the styled-only components, a dialog needs behavior: focus trap, scroll\nlock, Esc-to-close, click-outside dismissal, and the full WAI-ARIA keyboard contract. All of it comes\nfrom the platform via showModal() — no state-machine dependency and no adapter to wire. The styled\nOriDialog supplies only the markup and tokens.",{"path":45,"title":46,"description":47},"\u002Fcomponents\u002Fdivider","Divider","A horizontal (default) or vertical rule that separates content. An optional centered label turns it\ninto a visual break like the classic \"OR\" between form sections. A pure layout\u002Fstructure primitive —\nno interactive behavior, no variants, no size scale.",{"path":49,"title":50,"description":51},"\u002Fcomponents\u002Fdrawer","Drawer","A panel docked to one edge of the viewport: a filter sheet, a settings pane, a cart, the navigation on a phone.\nIt runs on the same useDialog engine and the same native \u003Cdialog> element as OriDialog,\nso what a dialog gets from the platform, a drawer gets too. Opened modally (the default) it uses\nshowModal(): a backdrop, a focus trap, an inert page, Esc to close and focus returned to whatever opened it.\nOpened non-modally it is a manual popover, so it still sits in the top layer while the page behind stays\nlive. Swipe to dismiss, snap points and nested drawers are not in this version.",{"path":53,"title":54,"description":55},"\u002Fcomponents\u002Ffield","Field","The shared shell for form controls — one source of truth for the label \u002F hint \u002F error \u002F\nrequired contract that Input, Select,\nTextarea, Combobox, Slider,\nRadioGroup, SegmentedControl and\nColorPicker otherwise each wire\nby hand. Wrap a control in OriField and it adopts the field's id, aria-describedby,\naria-invalid, required, disabled, and size — and stops rendering its own label and helper, so\nthere is exactly one of each, wired identically every time. Group and composite controls (RadioGroup,\nSegmentedControl, Combobox's listbox, ColorPicker) name themselves via aria-labelledby pointing at the field's label.",{"path":57,"title":58,"description":59},"\u002Fcomponents\u002Ficon","Icon","A styled, accessible SVG icon. Decorative by default — renders with aria-hidden=\"true\" and no\nrole. Pass a label to expose it to assistive technology as an image: the icon switches to\nrole=\"img\" + aria-label automatically.",{"path":61,"title":62,"description":63},"\u002Fcomponents\u002Finput","Input","A labeled, accessible text field with v-model. State is expressed through real attributes — the\nnative disabled, aria-invalid when there is an error, and an aria-describedby that points at\nthe rendered hint or error. The label is wired to the field with for\u002Fid (auto-generated via\nuseId when you don't pass one), and arbitrary native attributes (name, autocomplete,\ninputmode, …) fall through to the underlying \u003Cinput>.",{"path":65,"title":66,"description":67},"\u002Fcomponents\u002Fjoin","Join","A thin wrapper that collapses the shared radii and borders of adjacent controls so they read as one\nsegmented unit — button groups, input+button combos, segmented toolbars. No visual styling of its\nown: all color, size, and variant tokens live on the children.",{"path":69,"title":70,"description":71},"\u002Fcomponents\u002Fkbd","Kbd","A keyboard-key chip — a semantic \u003Ckbd> element styled as a monospace bordered chip. Use it to\nrepresent individual keys, modifier keys, or multi-key shortcuts inline in prose or UI hints.",{"path":73,"title":74,"description":75},"\u002Fcomponents\u002Flink","Link","An inline prose link — the right choice when a destination lives in running text. Distinct from\nOriButton rendered as=\"a\": a button that navigates is still a button; a link in a sentence is\nOriLink. Underlined by default (the affordance survives without color), with a _hover mode that\nhides the underline at rest and reveals it on hover. A visible :focus-visible ring uses the same\ncolor as the text.",{"path":77,"title":78,"description":79},"\u002Fcomponents\u002Flist","List","A vertical list of rows for settings panels, action panels and navigation. Each row reads prepend → label →\nappend: an icon, a label with an optional subtitle, and at the end short meta text such as a shortcut, a\nchevron into a sub-panel, or a control of your own.",{"path":81,"title":82,"description":83},"\u002Fcomponents\u002Fmenu","Menu","A WAI-ARIA menu button: a trigger opens a roving-tabindex action list. Unlike the Popover, open\u002Fclose,\nfocus movement, and click-outside dismissal are driven entirely by the @oriui\u002Fheadless menu\nmachine in JavaScript. OriMenu still opens the panel in the top layer (popover=\"manual\" +\nshowPopover()), so an ancestor's transform, overflow or z-index cannot displace or clip it, and\nplaces it with the same CSS Anchor Positioning primitive as the Popover (ori-anchored), zero\npositioning JS. In your own markup, do the same; without popover the panel falls back to its z-index.",{"path":85,"title":86,"description":87},"\u002Fcomponents\u002Fpopover","Popover","A positioned overlay for supplementary content — a menu, a filter panel, a rich hint — tethered to a\ntrigger. It runs entirely on the platform: the trigger opens the panel through the Popover API\n(top-layer, light-dismiss, Esc — zero JS), and the panel is placed with CSS Anchor Positioning\n(anchor-name \u002F position-anchor + position-area, with a collision flip via\nposition-try-fallbacks) — zero positioning JS, no scroll\u002Fresize listeners. Baseline 2026, with\ngraceful degradation: an older engine still opens the panel and places it, just without the\ncollision-aware flip.",{"path":89,"title":90,"description":91},"\u002Fcomponents\u002Fprogress","Progress","A horizontal progress bar that communicates task completion. It supports a determinate mode (a\nknown value out of a max) and an indeterminate mode (animated sweep) for tasks with no\nmeasurable progress. State is expressed through ARIA attributes — aria-valuenow is omitted when\nindeterminate, giving screen readers the correct cue automatically.",{"path":93,"title":94,"description":95},"\u002Fcomponents\u002Fradio","Radio","A \"choose one\" compound control. A role=\"radiogroup\" container names the set via\naria-labelledby; each option is a real \u003Cinput type=\"radio\"> sharing a single name — so the\nbrowser enforces single-select and native form submission — visually hidden behind a styled circle.\nPass the options as an array; per-option disabled is supported.\nFor a short pick shown as one compact row of buttons (Light \u002F Dark \u002F Auto), use\nSegmentedControl: the same radio semantics, styled as segments.",{"path":97,"title":98,"description":99},"\u002Fcomponents\u002Fsegmented-control","Segmented control","A compact \"choose one\" row — Light \u002F Dark \u002F Auto. It is built like RadioGroup: a\nrole=\"radiogroup\" of real \u003Cinput type=\"radio\"> sharing one name, each input hidden over its segment.\nSo the browser gives you the behavior — arrow keys that move and select, a single Tab stop on the checked\nsegment, native form submission and RTL — and the CSS layer carries no JavaScript at all.",{"path":101,"title":102,"description":103},"\u002Fcomponents\u002Fselect","Select","A native-first styled select control with v-model. The browser owns the dropdown, full keyboard\ninteraction, type-ahead, and all ARIA semantics — oriUI only styles the closed control and draws a\ndecorative chevron. It shares the form-control contract of Input and\nTextarea: a built-in label, hint, error, and required asterisk, all\nwired for accessibility. State is expressed through real attributes — native disabled and\naria-invalid=\"true\" (not classes) — and arbitrary native attrs (name, autocomplete, …) fall\nthrough to the \u003Cselect> via inheritAttrs:false.",{"path":105,"title":106,"description":107},"\u002Fcomponents\u002Fskeleton","Skeleton","A loading placeholder that signals content is on its way. An animated shimmer sweep sweeps across the\nblock; on devices that request reduced motion the shimmer stops and the tinted block alone signals the\nloading state. Size it with an inline style or a utility class — the skeleton itself carries no\nintrinsic width or height beyond a 1em minimum height.",{"path":109,"title":110,"description":111},"\u002Fcomponents\u002Fslider","Slider","A styled, accessible range control built on a native \u003Cinput type=\"range\">. Because the\nunderlying element is real HTML, the browser supplies role=\"slider\", the full keyboard contract\n(arrow keys, Home\u002FEnd, PageUp\u002FPageDown), and screen-reader value announcements for free — no\nJavaScript bridge needed. Color and the filled-track portion are driven by CSS custom properties;\nv-model carries a number.",{"path":113,"title":114,"description":115},"\u002Fcomponents\u002Fspinner","Spinner","An accessible loading indicator — renders role=\"status\" with an aria-label (default \"Loading\")\nso assistive technology announces the busy state without any extra work. Use it standalone for a\npage-level or section-level loader, or embed it inline inside a button or label.",{"path":117,"title":118,"description":119},"\u002Fcomponents\u002Fstack","Stack","The workhorse layout primitive — two flex modes in one component. A stack (ori-stack) is a\nflex column: children flow top-to-bottom with a consistent gap. A cluster (ori-cluster) is a\nwrapping flex row: children flow left-to-right, wrap onto new lines, and are centered on the\ncross-axis — ideal for tag clouds, button groups, and badge sets.",{"path":121,"title":122,"description":123},"\u002Fcomponents\u002Fsurface","Surface","An elevated floating surface — a lifted panel with a surface background, an optional hairline, a\ncorner radius, and a mode-aware shadow, and nothing else. No padding, no header\u002Ftitle semantics: it\nis just the box, and the caller owns the layout inside. It's the building block for chrome that floats\nover content — a toolbar island, a zoom control, a side panel, a menu popout's container — and the\nelevation counterpart to Card, which is a content card (padding + header \u002F\ntitle \u002F body \u002F actions).",{"path":125,"title":126,"description":127},"\u002Fcomponents\u002Fswitch","Switch","An on\u002Foff toggle built on a real \u003Cinput type=\"checkbox\" role=\"switch\"> — kept in the DOM\n(visually hidden over a track + thumb) so keyboard, focus, and form submission work for free, and\nassistive technology announces it as a switch. v-model is a boolean. The \"on\" track color and the\n:focus-visible ring both come from the ori-color token; the track and thumb scale with\nori-font-size so size is a single prop.",{"path":129,"title":130,"description":131},"\u002Fcomponents\u002Ftable","Table","A styled native \u003Ctable>: a rule under the header row, hairlines between body rows, start-aligned cells, and a few\nmodifiers for stripes, a hover tint, a sticky header and cell density. The CSS layer works on any \u003Ctable> with\nno JavaScript; OriTable adds the caption and the accessibility of the box a wide table scrolls in.",{"path":133,"title":134,"description":135},"\u002Fcomponents\u002Ftabs","Tabs","An accessible tabs widget with automatic activation. The tablist holds a roving tabindex so\nTab \u002F Shift+Tab enter and leave the group as a single keyboard stop; arrow keys move between\ntabs and immediately select them. State is expressed through real ARIA attributes — aria-selected\ndrives both the active indicator and the label color; disabled is the native button attribute.",{"path":137,"title":138,"description":139},"\u002Fcomponents\u002Ftag","Tag","A compact label for categorizing, filtering, or annotating content — status chips, keyword\nbadges, and removable filter pills. State is expressed through real attributes: aria-disabled\ndisables the tag and its close button without removing it from the DOM.",{"path":141,"title":142,"description":143},"\u002Fcomponents\u002Ftextarea","Textarea","A labeled, accessible multiline text field with v-model. State is expressed through real\nattributes — the native disabled, aria-invalid when there is an error, and an aria-describedby\nthat points at the rendered hint or error. The label is wired to the field with for\u002Fid\n(auto-generated via useId when you don't pass one). Unlike a single-line input the field has no\nfixed height — it grows from a rows-based min-height and stays user-resizable.",{"path":145,"title":146,"description":147},"\u002Fcomponents\u002Ftoast","Toast","An imperative notification system. Push a toast from anywhere with useToast() and render\n\u003COriToaster \u002F> once near the app root to display the queue. No event bus, no Vuex, no provide\u002Finject —\njust a module-level reactive queue that every call site shares.",{"path":149,"title":150,"description":151},"\u002Fcomponents\u002Ftoolbar","Toolbar","A WAI-ARIA toolbar: a set of related controls that share a single Tab stop, navigated internally\nwith the arrow keys via roving tabindex (real DOM focus, not aria-activedescendant). Five\ncomponents make it up — OriToolbar (the root, role=\"toolbar\"), OriToolbarButton (an item —\ncomposes OriButton), OriToolbarSeparator (a perpendicular divider), and a paired\nOriToolbarToggleGroup \u002F OriToolbarToggleItem for a segmented single- or multi-select toggle.\nUnlike the data-driven OriMenu (an items array plus a machine), a toolbar is compositional —\nyou assemble it from slotted components in whatever order and combination you need — so the behavior\nunderneath, useToolbar from @oriui\u002Fheadless, is a provide\u002Finject\nroving-focus context rather than a state machine over an array.",{"path":153,"title":154,"description":155},"\u002Fcomponents\u002Ftooltip","Tooltip","A CSS-driven tooltip that shows additional context when a control is focused or hovered. The bubble\nis always in the DOM (so the aria-describedby reference is never dangling) and shown\u002Fhidden in CSS —\nno state machine, no positioning engine. Show is :focus-visible (keyboard focus) and :hover wrapped\nin @media (hover: hover) (pointer, without sticking open on touch); a click or a tap that focuses the\ntrigger does not show it. A press of the trigger hides it, the pointer can move onto the bubble, and\nEscape hides it without moving focus or the pointer (WCAG 1.4.13).",{"path":157,"title":158,"description":159},"\u002Fguides\u002Fcss","Using the CSS layer","The @oriui\u002Fcss package is oriUI's foundation: standalone .ori-* classes plus the token theming — no Vue, no build step, no Tailwind. You\nship the stylesheet and write classes. This is how oriUI works with htmx, Astro, or plain HTML —\nthe daisyUI niche, minus Tailwind.",{"path":161,"title":162,"description":163},"\u002Fguides\u002Fcustomization","Customization","Make it yours — without authoring a whole skin. Most products need one thing: their brand color and\ntheir corner radius on top of accessible, ready-made components. oriUI lets you do that by repointing\na handful of design tokens — a few CSS custom properties in your own stylesheet, no rewrite, no fork.\nThe same \u003COriButton> you shipped on day one becomes on-brand by the time you ship to users, and\nnothing about the component changes.",{"path":165,"title":166,"description":167},"\u002Fguides\u002Fdesign-tokens","Design tokens","Every oriUI package reads one set of design tokens. This page is the\ncatalog — every token, and the resolution model that turns a raw value into the color a component\npaints. The chain is short and deliberate: a primitive feeds a semantic role, a role feeds a\nper-instance alias, and components read only the alias. That indirection is what lets a single\nclass repoint a single token — the whole zero-runtime theming story rests on it.",{"path":169,"title":170,"description":171},"\u002Fguides\u002Frtl","Writing direction (RTL)","oriUI's style layer is written in logical properties — margin-inline, border-block,\ninset-inline-end, position-area — so it follows the writing direction the platform gives it. You\nturn RTL on the platform way, and the layer mirrors itself:",{"path":173,"title":174,"description":175},"\u002Fguides\u002Fskins","Skin gallery","A skin is a named palette — a set of token overrides applied with one attribute on \u003Chtml>\n(data-ori-skin). Every skin repoints only the four skinnable roles (primary · secondary ·\nsurface · background, each with a -light and -dark source); the status hues (success ·\nwarning · danger · info) stay shared, and every pairing targets WCAG AA for body text. Switching\na skin is a single attribute write — zero runtime, no recompute, no flash.",{"path":177,"title":178,"description":179},"\u002Fguides\u002Ftheming","Theming","A theme is a mode (light or dark) layered over a skin (a named palette). Both are pure\nattribute toggles on \u003Chtml> — flipping either repoints the active --ori-color-* aliases through\nCSS custom properties, so everything reskins at once with no JavaScript, no recompute, no flash.\nThis is the same zero-runtime story across every layer: a Vue app, the standalone @oriui\u002Fcss\nclasses, htmx fragments, or hand-written HTML all theme identically.",{"path":181,"title":182,"description":183},"\u002Fheadless\u002Fcore","Core","The framework-agnostic heart of the headless layer: a behavior contract plus a zero-dependency\nnative engine, written in vanilla TypeScript. Every framework binding consumes the same contract,\nso a primitive behaves identically wherever it runs — and the behavior stays swappable per primitive,\nwithout touching markup.",{"path":185,"title":186,"description":187},"\u002Fheadless\u002Fuse-color-picker","useColorPicker","A headless sRGB color picker — a 2D saturation × brightness area, a hue channel, an optional\nalpha channel, a hex field, and optional preset swatches, assembled from ready-to-bind\nprop-getters. It owns the working color as an internal HSVA object (so the hue survives a grayscale\nround-trip when you drag into a corner and back). Underneath is a zero-dependency sRGB engine — a loose\nparser and a lowercase formatter, hex \u002F rgb \u002F hsv \u002F hsl conversion, readable ink over a swatch by WCAG\nluminance — and the 2D-area math for pointer and keyboard. That engine is internal: it ships inside this\ncomposable, not as exports of its own.",{"path":189,"title":190,"description":191},"\u002Fheadless\u002Fuse-combobox","useCombobox","A headless combobox primitive — an editable text input paired with a popup listbox — implementing\nthe WAI-ARIA combobox with listbox popup pattern: type to filter, navigate with the keyboard via\nactive-descendant, and pick a single option. It owns the behavior (open\u002Fclose, filtering, the\nhighlight, selection, and the full keyboard) and the ARIA wiring as ready-to-bind prop bags; you own\nthe markup and styles.",{"path":193,"title":194,"description":195},"\u002Fheadless\u002Fuse-dialog","useDialog","A headless modal dialog primitive built on the native \u003Cdialog> element — focus trap, Escape to\nclose, focus return, and aria-modal semantics all come from the platform via showModal(). It owns the open state and the ARIA wiring as ready-to-bind prop bags; you own the\nmarkup and styles (you render the \u003Cdialog> and drive showModal() \u002F close() from open).",{"path":197,"title":198,"description":199},"\u002Fheadless\u002Fuse-disclosure","useDisclosure","A headless show \u002F hide primitive for disclosure widgets — expandable panels, accordions, menus,\nthe collapsible sidebar groups on this very site. It owns the open state, the WAI-ARIA wiring, and the\ntoggle handler; you own the markup and the styles.",{"path":201,"title":202,"description":203},"\u002Fheadless\u002Fuse-dismissable","useDismissable","A headless dismiss layer — the \"close the overlay on an outside interaction\" glue a non-platform\noverlay needs, the pattern Radix DismissableLayer \u002F Floating-UI useDismiss standardize. While\nenabled, it attaches document listeners and calls onDismiss() when an interaction lands outside\nthe overlay's own elements. Both triggers are on by default — a pointerdown outside\n(pointerDownOutside) and focus moving outside (focusOutside) — and an overlay turns off the one that\ndoes not fit it:",{"path":205,"title":206,"description":207},"\u002Fheadless\u002Fuse-menu","useMenu","A headless menu button primitive built on the WAI-ARIA menu-button pattern — a trigger that opens a\npopup menu of actions, with roving tabindex, arrow \u002F Home \u002F End navigation, and Enter \u002F Space\nactivation. It owns the open state and the highlighted item and exposes the ARIA wiring as ready-to-bind\nprop bags; you own the markup, the styles, and the DOM focus (roving needs real focus, and\nclick-outside \u002F focus-return are host concerns a state projection can't reach).",{"path":209,"title":210,"description":211},"\u002Fheadless\u002Fuse-tabs","useTabs","A headless WAI-ARIA tabs widget with automatic activation — a tablist of tabs behind a single\nTab stop, navigated with the arrow keys via roving tabindex (real DOM focus, not\naria-activedescendant), where moving focus also selects. It is data-driven: you pass the tabs\narray plus the selected value, and it returns the tablist prop bag plus per-tab and per-panel\nprop-getters (ids, aria-selected, aria-controls, aria-labelledby, roving tabindex, hidden).",{"path":213,"title":214,"description":215},"\u002Fheadless\u002Fuse-theme","useTheme","A headless light \u002F dark theme controller — it owns the mode setting, resolves auto against the OS\nscheme live, persists the choice, and applies it to the DOM. It applies through applyTheme, which sets\nthe ori-theme_{light,dark} class (removing the opposite — exactly one is on at a time) and works\naround a bug in current Chromium where a runtime theme toggle otherwise leaves styled components\npainting the previous theme's colors until they re-render.",{"path":217,"title":218,"description":219},"\u002Fheadless\u002Fuse-toast","useToast","A headless toast queue — an imperative notification store you call from anywhere (toast('Saved'))\nand render once near the app root. The behavior is a framework-agnostic engine (a plain array + a Set\nof listeners + auto-dismiss timers) projected into the host framework's reactivity (in Vue, a reactive\narray). It is a client-side singleton — every useToast() call shares the one queue, so a push from\nanywhere reaches the single renderer.",{"path":221,"title":222,"description":223},"\u002Fheadless\u002Fuse-token","useToken","A reactive token bridge — it resolves an --ori-* design token to its computed value in JS, for\ncanvas \u002F WebGL \u002F chart painters (Konva, ECharts, …) that draw outside the CSS cascade yet must follow the\nactive skin. It reads through a hidden probe, because the obvious API is a trap: getComputedStyle(el).getPropertyValue('--x') hands back the unresolved var() chain (oriUI aliases chain), not a color —\nsubstitution only happens at a real property's computed-value time.",{"path":225,"title":226,"description":227},"\u002Fheadless\u002Fuse-toolbar","useToolbar","A headless WAI-ARIA toolbar — a set of related controls behind a single Tab stop, navigated\ninternally with the arrow keys via roving tabindex (real DOM focus, not aria-activedescendant).\nThe root owns orientation \u002F loop \u002F direction and a single keydown handler; each item registers itself\nand receives its roving tabindex, so a toolbar is assembled from arbitrary slotted components\nrather than a fixed data array.",{"path":229,"title":230,"description":231},"\u002Foverview\u002Faccessibility","Accessibility","Accessibility in oriUI is structural, not a coat of polish on top. The same decisions that make\nthe components correct for assistive technology also make them themeable and framework-agnostic — they\nare the same source of truth, not a separate effort.",{"path":233,"title":234,"description":235},"\u002Foverview\u002Fapplicability","Applicability","Where each oriUI package runs. The CSS works everywhere, the components are Vue, and the headless\ncomposables have a Vue adapter.",{"path":237,"title":238,"description":239},"\u002Foverview\u002Fcheat-sheet","Cheat sheet","Everything in one page — install, the class model, every component, and the design tokens. For the\nmachine-readable version (e.g. to paste into an AI), fetch \u002Fllms.txt (index) or\n\u002Fllms-full.txt (every page concatenated).",{"path":241,"title":242,"description":243},"\u002Foverview\u002Fcomparisons","Comparisons","oriUI combines three things that usually come separately: a CSS design system that needs no JavaScript,\nstyled Vue components, and headless behavior. This page sets it next to the libraries it learns from.\nIt has fewer components than most of them: we add one when an app built on oriUI needs it.",{"path":245,"title":246,"description":247},"\u002Foverview\u002Fget-started","Get started","Install oriUI and put a component on screen. Use only the packages you need.",{"path":249,"title":250,"description":251},"\u002Foverview\u002Finstallation","Installation","oriUI is three layers, one package each. Install only the layer you need — they share one token\ncontract, so you can add another later without reworking what you built.",{"path":253,"title":254,"description":255},"\u002Foverview\u002Fintroduction","Introduction","oriUI (織り, ori, \"weaving\") is a design system in plain CSS, with accessible Vue 3 components built\non it. It is made for our own apps first, so a component is added when one of them needs it.",{"path":257,"title":258,"description":259},"\u002Foverview\u002Fshowcase","Showcase","Apps built with oriUI. Each entry says what the app does and which parts of oriUI it uses, so you can see the\nlibrary inside a whole product, not one component at a time.",{"id":261,"title":170,"body":262,"description":171,"extension":928,"meta":929,"navigation":930,"path":169,"seo":931,"stem":932,"__hash__":933},"docs\u002Fguides\u002Frtl.md",{"type":263,"value":264,"toc":920},"minimark",[265,269,294,345,376,389,408,413,515,519,531,590,594,608,725,740,744,758,779,782,785,829,884,888,916],[266,267,170],"h1",{"id":268},"writing-direction-rtl",[270,271,272,273,277,278,282,283,286,287,282,290,293],"p",{},"oriUI's style layer is written in ",[274,275,276],"strong",{},"logical properties"," — ",[279,280,281],"code",{},"margin-inline",", ",[279,284,285],{},"border-block",",\n",[279,288,289],{},"inset-inline-end",[279,291,292],{},"position-area"," — so it follows the writing direction the platform gives it. You\nturn RTL on the platform way, and the layer mirrors itself:",[295,296,301],"pre",{"className":297,"code":298,"language":299,"meta":300,"style":300},"language-html shiki shiki-themes github-light github-dark","\u003Chtml dir=\"rtl\">\n    …\n\u003C\u002Fhtml>\n","html","",[279,302,303,329,335],{"__ignoreMap":300},[304,305,308,312,315,319,322,326],"span",{"class":306,"line":307},"line",1,[304,309,311],{"class":310},"sVt8B","\u003C",[304,313,299],{"class":314},"s9eBZ",[304,316,318],{"class":317},"sScJk"," dir",[304,320,321],{"class":310},"=",[304,323,325],{"class":324},"sZZnC","\"rtl\"",[304,327,328],{"class":310},">\n",[304,330,332],{"class":306,"line":331},2,[304,333,334],{"class":310},"    …\n",[304,336,338,341,343],{"class":306,"line":337},3,[304,339,340],{"class":310},"\u003C\u002F",[304,342,299],{"class":314},[304,344,328],{"class":310},[295,346,348],{"className":297,"code":347,"language":299,"meta":300,"style":300},"\u003C!-- or one region, inside an otherwise-LTR page -->\n\u003Csection dir=\"rtl\">…\u003C\u002Fsection>\n",[279,349,350,356],{"__ignoreMap":300},[304,351,352],{"class":306,"line":307},[304,353,355],{"class":354},"sJ8bj","\u003C!-- or one region, inside an otherwise-LTR page -->\n",[304,357,358,360,363,365,367,369,372,374],{"class":306,"line":331},[304,359,311],{"class":310},[304,361,362],{"class":314},"section",[304,364,318],{"class":317},[304,366,321],{"class":310},[304,368,325],{"class":324},[304,370,371],{"class":310},">…\u003C\u002F",[304,373,362],{"class":314},[304,375,328],{"class":310},[270,377,378,379,382,383,388],{},"There is no ",[279,380,381],{},"dir"," prop to thread through the styled components. Arrow keys follow the direction too\n(see ",[384,385,387],"a",{"href":386},"#keyboard-and-text","Keyboard and text",").",[270,390,391,392,395,396,399,400,403,404,407],{},"Everything on this page is ",[274,393,394],{},"measured",", not intended. ",[279,397,398],{},"e2e\u002Frtl.spec.ts"," renders the same markup under\n",[279,401,402],{},"dir=\"ltr\""," and ",[279,405,406],{},"dir=\"rtl\""," in real Chromium, Firefox and WebKit and asserts bounding boxes and computed values — never\nclass names, because a logical property only resolves against a real writing direction in a real\nengine.",[409,410,412],"h2",{"id":411},"what-mirrors","What mirrors",[414,415,416,429],"table",{},[417,418,419],"thead",{},[420,421,422,426],"tr",{},[423,424,425],"th",{},"Component",[423,427,428],{},"The measured contract",[430,431,432,445,453,465,482,492,500,507],"tbody",{},[420,433,434,438],{},[435,436,437],"td",{},"Vertical tabs",[435,439,440,441,444],{},"The tab list leads on the inline-start side, its 1px rule faces the panel, and the selected-tab indicator lands on that ",[274,442,443],{},"same"," edge.",[420,446,447,450],{},[435,448,449],{},"Vertical divider",[435,451,452],{},"The rule is drawn strictly between its two siblings, whichever way round they run.",[420,454,455,458],{},[435,456,457],{},"Floating badge",[435,459,460,461,464],{},"The badge centers on the anchor's inline-",[274,462,463],{},"end"," top corner and overhangs outward — physically right in LTR, physically left in RTL. It never folds back in.",[420,466,467,470],{},[435,468,469],{},"Anchored panels",[435,471,472,473,476,477,481],{},"The whole ",[279,474,475],{},".ori-anchored_*"," grid is logical. See ",[384,478,480],{"href":479},"#placement-names-read-physical-behave-logical","placement names"," below.",[420,483,484,486],{},[435,485,150],{},[435,487,488,489,491],{},"Children run in the inline direction; the separator stays between them with a symmetric ",[279,490,281],{}," gap.",[420,493,494,497],{},[435,495,496],{},"Select \u002F combobox field",[435,498,499],{},"The chevron and the padding reserved for it land on the same inline-end side, so the value text never runs under it.",[420,501,502,504],{},[435,503,126],{},[435,505,506],{},"The thumb rests at the inline-start end when off and travels to the inline-end end when on, staying inside its track in both directions.",[420,508,509,512],{},[435,510,511],{},"Toast accent stripe",[435,513,514],{},"The 4px accent border sits on the leading edge — left in LTR, right in RTL.",[409,516,518],{"id":517},"what-stays-physical-on-purpose","What stays physical — on purpose",[270,520,521,522,526,527,530],{},"Not everything that ",[523,524,525],"em",{},"can"," mirror ",[523,528,529],{},"should",". Three things are deliberately pinned to the screen, and the\nsame suite asserts they stay that way so a future \"helpful\" logical swap has to be a deliberate one.",[532,533,534,557,574],"ul",{},[535,536,537,540,541,544,545,548,549,552,553,556],"li",{},[274,538,539],{},"The six toaster corners."," ",[279,542,543],{},"ori-toaster_top-left"," … ",[279,546,547],{},"ori-toaster_bottom-right"," name a ",[274,550,551],{},"screen","\ncorner, not an inline position, so a left-pinned toaster is on the left in both directions. The\nenter animation follows the corner it is pinned to, sliding in off that physical edge. A toaster\nwith ",[274,554,555],{},"no"," corner modifier is the one case with no physical edge to follow — it enters from the\ninline-end side, so that one does read the direction.",[535,558,559,562,563,565,566,569,570,573],{},[274,560,561],{},"The color-picker value plane."," The saturation × brightness area is a value plane, not text: its\ngradient runs to the physical right, ",[279,564,186],{}," places the thumb with a physical ",[279,567,568],{},"left","\npercentage, and the pointer handler measures ",[279,571,572],{},"clientX - rect.left",". All three are physical and must\nstay consistent with one another, so full saturation is the physical right edge in both directions.",[535,575,576,540,579,282,582,585,586,589],{},[274,577,578],{},"The safe-area utilities.",[279,580,581],{},".ori-safe-area",[279,583,584],{},".ori-safe-area_inline"," and friends pass\n",[279,587,588],{},"env(safe-area-inset-*)"," through to physical padding. A notch and a home indicator are physical\nhardware; mirroring them would move the padding away from the cutout.",[409,591,593],{"id":592},"placement-names-read-physical-behave-logical","Placement names read physical, behave logical",[270,595,596,597,600,601,604,605,607],{},"The placement modifiers on ",[279,598,599],{},".ori-anchored"," — shared by Popover, Menu, Tooltip and Combobox — have\nphysical-sounding names and ",[274,602,603],{},"logical"," behavior, because ",[279,606,292],{}," is a logical property:",[414,609,610,626],{},[417,611,612],{},[420,613,614,617,620,623],{},[423,615,616],{},"Class",[423,618,619],{},"Resolves to",[423,621,622],{},"LTR",[423,624,625],{},"RTL",[430,627,628,649,668,689,708],{},[420,629,630,635,640,643],{},[435,631,632],{},[279,633,634],{},".ori-anchored_left",[435,636,637],{},[279,638,639],{},"position-area: inline-start",[435,641,642],{},"left of the trigger",[435,644,645,648],{},[274,646,647],{},"right"," of the trigger",[420,650,651,656,661,664],{},[435,652,653],{},[279,654,655],{},".ori-anchored_right",[435,657,658],{},[279,659,660],{},"position-area: inline-end",[435,662,663],{},"right of the trigger",[435,665,666,648],{},[274,667,568],{},[420,669,670,675,680,683],{},[435,671,672],{},[279,673,674],{},".ori-anchored_bottom-start",[435,676,677],{},[279,678,679],{},"block-end span-inline-end",[435,681,682],{},"aligns to the left edge",[435,684,685,686,688],{},"aligns to the ",[274,687,647],{}," edge",[420,690,691,696,701,704],{},[435,692,693],{},[279,694,695],{},".ori-anchored_bottom-end",[435,697,698],{},[279,699,700],{},"block-end span-inline-start",[435,702,703],{},"aligns to the right edge",[435,705,685,706,688],{},[274,707,568],{},[420,709,710,715,720,723],{},[435,711,712],{},[279,713,714],{},".ori-anchored_bottom",[435,716,717],{},[279,718,719],{},"block-end",[435,721,722],{},"centered on the trigger",[435,724,722],{},[270,726,727,728,731,732,735,736,739],{},"So ",[279,729,730],{},"placement=\"left\""," means ",[274,733,734],{},"inline-start",", and reads as \"before the trigger in reading order\". The\nbare sides stay centered on the trigger in both directions, and the gap is a ",[279,737,738],{},"margin-inline-*",", so it\nopens on the correct side too.",[409,741,743],{"id":742},"the-slider-family-follows-the-engine","The slider family follows the engine",[270,745,746,747,750,751,753,754,757],{},"A native ",[279,748,749],{},"\u003Cinput type=\"range\">"," reverses itself under ",[279,752,406],{}," in Chromium: click a quarter of the\nway in from the physical left and the control resolves a value ",[274,755,756],{},"above"," the midpoint, because the\nengine now treats the right edge as the minimum. That is the platform's behavior, not oriUI's — so\nthe paint oriUI draws over the control follows it rather than arguing with it. Measured from the real\npixels:",[532,759,760,767,773],{},[535,761,762,763,766],{},"the ",[274,764,765],{},"fill"," starts at the end the engine treats as the minimum, so fill and thumb always agree;",[535,768,762,769,772],{},[274,770,771],{},"hue"," spectrum runs along the engine's own axis;",[535,774,762,775,778],{},[274,776,777],{},"alpha"," ramp is opaque at the end the engine treats as the maximum.",[270,780,781],{},"The color picker inherits all three through the hue and alpha sliders it composes — which is a\nseparate question from its value plane above, and resolved the other way.",[409,783,387],{"id":784},"keyboard-and-text",[270,786,787,788,791,792,794,795,403,797,799,800,802,803,806,807,809,810,813,814,817,818,821,822,817,825,828],{},"Arrow keys in a horizontal row follow the layout: in RTL the first item is on the right, so\n",[279,789,790],{},"ArrowLeft"," moves to the next one. Tabs, Toolbar and the color picker's presets read the direction\nthey are laid out in when a key is pressed, so an ancestor ",[279,793,406],{}," is all they need.\n",[279,796,210],{},[279,798,226],{}," also take a ",[279,801,381],{}," option (and ",[279,804,805],{},"\u003COriToolbar>"," a ",[279,808,381],{}," prop) that sets\nthe direction on the widget itself. ",[279,811,812],{},"e2e\u002Frtl-keyboard.spec.ts"," checks this in Chromium, Firefox and WebKit. Vertical\nnavigation (",[279,815,816],{},"ArrowUp"," \u002F ",[279,819,820],{},"ArrowDown",") and ",[279,823,824],{},"Home",[279,826,827],{},"End"," do not depend on direction.",[270,830,831,832,835,836,817,839,842,843,846,847,850,851,282,854,282,857,282,860,282,863,403,866,842,869,872,873,403,876,879,880,883],{},"Direction is not ",[274,833,834],{},"text",": oriUI ships no translations and no message catalog. Most built-in strings are\nprops with English defaults you override — ",[279,837,838],{},"OriSpinner",[279,840,841],{},"OriProgress"," take ",[279,844,845],{},"label"," (",[279,848,849],{},"'Loading'","), and\n",[279,852,853],{},"OriAlert",[279,855,856],{},"OriTag",[279,858,859],{},"OriDialog",[279,861,862],{},"OriDrawer",[279,864,865],{},"OriToast",[279,867,868],{},"OriToaster",[279,870,871],{},"closeLabel",", and\n",[279,874,875],{},"OriColorPicker",[279,877,878],{},"OriCombobox"," take a ",[279,881,882],{},"labels"," object that names their parts.",[409,885,887],{"id":886},"see-also","See also",[532,889,890,895,903],{},[535,891,892,894],{},[384,893,158],{"href":157}," — the standalone classes these blocks come from.",[535,896,897,899,900,902],{},[384,898,162],{"href":161}," — scoping tokens to a subtree, the same way ",[279,901,381],{}," scopes.",[535,904,905,907,908,907,910,912,913,915],{},[384,906,146],{"href":145}," · ",[384,909,86],{"href":85},[384,911,110],{"href":109}," ·\n",[384,914,34],{"href":33}," — the components with a direction story of their own.",[917,918,919],"style",{},"html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .s9eBZ, html code.shiki .s9eBZ{--shiki-default:#22863A;--shiki-dark:#85E89D}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}",{"title":300,"searchDepth":331,"depth":331,"links":921},[922,923,924,925,926,927],{"id":411,"depth":331,"text":412},{"id":517,"depth":331,"text":518},{"id":592,"depth":331,"text":593},{"id":742,"depth":331,"text":743},{"id":784,"depth":331,"text":387},{"id":886,"depth":331,"text":887},"md",{},true,{"title":170,"description":171},"guides\u002Frtl","zu1_71Ww5G98DtGIzEzBlfuvU99TX6UVo5YzZDXLn_w",1791706811350]