Skip to content

Browser support

Which browsers TaishoDS Core supports and, feature by feature, what relies on the modern platform and what has a fallback. The system bets heavily on recent APIs. This matrix is the honest statement of where it degrades and where it doesn’t.

Policy

Baseline widely available: the Core’s floor is the Chrome, Edge, Firefox, and Safari versions (iOS included) that already have what that level requires, about 30 months after they shipped. Today that is Chrome and Edge 124, Firefox 125, and Safari 17.4 (per the data of November 10, 2026). Nothing is promised below that floor. Anything above it has an explicit fallback (CSS @supports and/or feature detection in JS) or degrades without breaking.

  • A feature within the floor is used directly, with no guard.
  • A feature above the floor is only used if it degrades safely—the browser ignores the unknown property, or there’s a fallback behind @supports / CSS.supports().
  • A positioning or color feature is never used without a guard if its absence leaves the component broken.
Baseline key: ✅ Widely available (works across the whole floor) · 🟢 Newly available (all 4 engines ship it, but one of them after the floor’s versions) · 🟡 Pre-Baseline (still missing in some engine). The statuses come from MDN browser-compat-data.

Overlays and the top layer

Feature Where it’s used Baseline Fallback
<dialog> + showModal()Modal, Drawer, AlertDialog✅ Widely availableNone—native focus trap, top layer, and ::backdrop
Popover APIMenu, Popover, Tooltip, Select, Combobox, ContextMenu, NavBar, Toaster✅ Widely available (Chrome 114, Firefox 125, Safari 17)Feature detection ('showPopover' in element) → position: fixed
inertOverlays (blocking the background)✅ Widely available (2023)None needed
Invoker commands (command / commandfor)Modal, Drawer (declarative opening)🟢 Newly available (2025: Chrome 135, Firefox 144, Safari 26.2)The behavior JS detects the missing support and runs show-modal, close and request-close on the dialog (command event, focus back to the trigger, Escape); with native support it does nothing
closedby (<dialog closedby="any">)Modal, Drawer (close on backdrop click)🟡 No Safari (Chrome 134, Firefox 141; Safari does not ship it yet)The behavior JS detects the missing support and closes a modal dialog with closedby="any" on a backdrop click (cancelable cancel event, then close, focus restored); it honors closerequest and none; with native support it does nothing

Positioning

The riskiest feature in the system—without it, an anchored overlay ends up in the wrong place. That’s why it’s guarded and has a JS fallback. If the browser doesn’t support the native path, the overlay is positioned with JavaScript and lands in the same spot.

Feature Where it’s used Baseline Fallback
CSS Anchor Positioning (anchor-name, anchor-scope, position-area, position-try)Every anchored overlay🟢 Newly available (2026: Chrome 131, Safari 26, Firefox 147)Guarded by @supports. Outside the guard, floating.ts (0 deps) with flip/shift

Color and theming

Feature Where it’s used Baseline Fallback
light-dark()Color tokens (everywhere)🟢 Newly available (2024: Chrome 123, Firefox 120, Safari 17.5)Per-mode values in an @supports not
oklch()Color tokens (source of truth)✅ Widely available (2023)None needed
color-mix()Materials / states✅ Widely available (2023)None needed
@media (color-gamut: p3)Display-P3 tokens (only the variables that differ from sRGB)✅ Widely availableNone—without P3 it’s ignored and the sRGB value stays
contrast-color()Badge with a custom color🟢 Newly available (2026: Chrome 147, Firefox 146, Safari 26)Guarded by @supports, with an oklch(from …) calculation before it and, before that, the tinted background with the theme text color
oklch(from …) (color relativo)Badge with a custom color (the calculation that precedes contrast-color)🟢 Newly available (2024: Chrome 119, Firefox 128, Safari 16.4)Guarded by @supports. Without relative color (Firefox 125–127) the badge is painted with the chosen color lightly tinted (color-mix over the background) and the theme text color, so contrast holds with any color

Layout, text, and inputs

Feature Where it’s used Baseline Fallback
Container queries (container-type, @container)NavBar, responsive Table, and the @sm: / @md: variants (with ts-cq)✅ Widely available (2023)None needed. Manual breakpoints are still available
text-wrap: balance / prettyHeadings (balance) and paragraphs (pretty)🟡 Pre-Baseline (pretty: Chrome 117, Safari 26, not yet in Firefox; balance is already newly available)Normal wrapping
:user-invalidInput, Textarea (error ring only after the field is touched)✅ Widely available (2023)None. Errors set by props/JS still work
field-sizing: contentTextarea (auto-resize)🟢 Newly available (2026: Chrome 123, Safari 26.2, Firefox 152)Feature detection with CSS.supports. Without support, the field keeps a fixed height
corner-shape: squircleCorner radius, with the theme's cornerShape: 'squircle' option🟡 Experimental (2025)Guarded by @supports. Without support it stays round, with the usual radii
scrollbar-width / scrollbar-colorScrollArea🟢 Newly available (scrollbar-color: Chrome 121, Firefox 64, Safari 26.2; scrollbar-width already from 18.2)The system’s native scrollbar
scrollbar-gutter: stableModal and Drawer (reserve the scrollbar space while the background is locked)🟢 Newly available (Chrome 94, Firefox 97, Safari 18.2)Without support the property is ignored: with a scrollbar that takes up space the page shifts a few pixels when the dialog opens because the bar disappears. The background stays locked and the dialog works the same
@propertyInternal ring and border variables (--ts-bw, --ts-ring-w, --ts-ring-c)🟢 Newly available (2024: Chrome 85, Firefox 128, Safari 16.4)Guarded by @supports: only in Firefox 125–127 (where @property does not exist) every element resets the three variables with initial, so they do not inherit into descendants; with @property nothing changes
backdrop-filterModal and Drawer backdrop, command palette and the backdrop-blur utilities🟢 Newly available (Chrome 76, Firefox 103, Safari 18; 17.4 to 17.6 only with the -webkit- prefix)The Core emits -webkit-backdrop-filter next to every backdrop-filter (in transitions too), so Safari 17.4–17.6 blurs the same
user-selectNon-selectable buttons, controls and surfaces (select-none utilities and components)🟡 Not in Safari (only with the -webkit- prefix)The Core emits -webkit-user-select next to every user-select, so in Safari the non-selectable text stays non-selectable
forced-color-adjustDatePicker (the selected day in forced-colors mode)🟡 Not in Safari (it has no forced-colors mode)None needed: where there is no forced-colors mode there is nothing to adjust
text-size-adjustReset (prevents text rescaling on mobile)🟡 Mobile only (also emitted with -webkit- and -moz-)None needed: it does not apply on desktop
view-transition-nameTabs (view-transition name of the active indicator)🟢 Newly available (Chrome 111, Safari 18, Firefox 144)Without support the property is ignored: the indicator changes without a transition

Animation

Feature Where it’s used Baseline Fallback
@starting-styleOverlay entry animations🟢 Newly available (2024: Chrome 117, Firefox 129, Safari 17.5)Appears without an entry animation
prefers-reduced-motionmotion.ts (follows the OS setting)✅ Widely availableN/A—it’s the guard itself

How it’s checked

The risky features (anchor-name, position-*, and contrast-color) only appear in the CSS behind an @supports. The rest of the features degrade on their own or have feature detection in JS, so they don’t need a guard. On top of that, continuous integration compares the Core’s CSS and JS with MDN’s data and fails if anything above the floor is missing from this table with its fallback or with what it loses.

The fallbacks are tested with real interaction in Chromium, WebKit, and Firefox, not in a simulated environment. See also Compatibility and Motion.