Appearance
Browser Support
Support matrix
| Browser | Minimum | Rationale |
|---|---|---|
| Chrome / Edge | 111 | oklch(), cascade layers, container queries |
| Firefox | 113 | oklch() |
| Safari (macOS) | 16.4 | Container queries, oklch() |
| Safari (iOS) | 16.4 | Same |
| Opera | 97 | Chromium 111 |
| Samsung Internet | 23 | Chromium 111 |
| Chrome Android | 111 | |
| Firefox Android | 113 |
Combined coverage: ~96.5% of global traffic, and typically 99%+ of admin-panel traffic, which skews heavily toward evergreen desktop browsers.
# .browserslistrc
chrome >= 111
edge >= 111
firefox >= 113
safari >= 16.4
ios_saf >= 16.4
not dead
not op_mini allNot supported
| Browser | Reason |
|---|---|
| Internet Explorer (any) | Discontinued June 2022. No custom properties, no grid support worth having. |
| Legacy Edge (≤ 18) | Discontinued March 2021 |
| Safari ≤ 16.3 | No container queries |
| Chrome ≤ 110 | No oklch() |
| Opera Mini | No JavaScript execution in extreme mode |
| Any browser without CSS Custom Properties | The entire token system depends on them |
Note — a legacy build targeting Chrome 91 / Safari 15 is available on request. It converts
oklch()to sRGB hex, polyfills container queries withcontainer-query-polyfill, and flattens cascade layers. It is 34% larger and loses runtime theming.
Required platform features
CSS
| Feature | Chrome | Firefox | Safari | Used for |
|---|---|---|---|---|
| Custom properties | 49 | 31 | 9.1 | Everything |
@layer | 99 | 97 | 15.4 | Cascade control |
oklch() | 111 | 113 | 15.4 | Colour system |
| Container queries | 105 | 110 | 16.0 | Component responsiveness |
:has() | 105 | 121 | 15.4 | Selection states |
| Logical properties | 89 | 66 | 15.0 | RTL |
inset shorthand | 87 | 66 | 14.1 | Positioning |
aspect-ratio | 88 | 89 | 15.0 | Media |
gap in flexbox | 84 | 63 | 14.1 | Layout |
color-scheme | 81 | 96 | 13 | Native dark UI |
content-visibility | 85 | 125 | 18 | Long lists (progressive) |
text-wrap: balance | 114 | 121 | 17.5 | Headings (progressive) |
@view-transition | 126 | — | 18 | Page transitions (progressive) |
The last four are progressive enhancements — the interface works without them.
JavaScript
| Feature | Used for |
|---|---|
ES modules + dynamic import() | Code splitting |
Proxy | Reactive store |
WeakMap | Instance registry |
AbortController / AbortSignal | Listener cleanup |
IntersectionObserver | Lazy init, scroll reveal, scrollspy |
ResizeObserver | Chart and grid resizing |
MutationObserver | Dynamic markup init |
CustomEvent | DOM event bridge |
structuredClone | Store snapshots |
| Optional chaining / nullish coalescing | Everywhere |
| Private class fields | Core internals |
Intl.* | All formatting |
No polyfills are shipped. Every listed feature is available in every supported browser.
Feature detection
Progressive enhancements are guarded, never assumed.
scss
@supports (backdrop-filter: blur(1px)) {
.av-glass { backdrop-filter: blur(var(--av-glass-blur)); }
}
@supports not (backdrop-filter: blur(1px)) {
.av-glass { background: var(--av-surface-raised); }
}
@supports (content-visibility: auto) {
.av-list--long > * { content-visibility: auto; contain-intrinsic-size: auto 64px; }
}
@supports (text-wrap: balance) {
h1, h2, h3 { text-wrap: balance; }
}js
// Feature-detect, never user-agent-sniff
if ('startViewTransition' in document) { /* … */ }
if (CSS.supports('color', 'oklch(50% 0.1 180)')) { /* … */ }
if ('requestIdleCallback' in window) { /* … */ } else { setTimeout(fn, 1); }User-agent sniffing is banned. It is wrong the moment a browser ships an update.
Known browser quirks
Safari
| Quirk | Workaround |
|---|---|
100vh includes collapsing toolbar chrome | Use 100dvh |
<use href> to an external SVG ignores inherited custom properties (< 16.4) | Inline the illustration sprite |
backdrop-filter needs -webkit- prefix (< 16) | Autoprefixer handles it |
| Date input styling is limited | Flatpickr for consistent appearance |
overflow: hidden on <body> does not always lock scroll on iOS | position: fixed scroll lock in the modal module |
Smooth scrolling ignores scroll-padding in some versions | scrollIntoView({ block: 'center' }) |
Momentum scroll fires no scroll events until it settles | Topbar auto-hide uses a threshold |
Firefox
| Quirk | Workaround |
|---|---|
No ::-webkit-scrollbar | scrollbar-width / scrollbar-color used first |
:has() only from 121 | Guarded with @supports selector(:has(*)) |
| Different default focus ring | Overridden globally |
<input type="number"> spinner styling differs | We avoid type="number" for most fields anyway |
Chrome / Edge
| Quirk | Workaround |
|---|---|
| Autofill background cannot be changed | -webkit-text-fill-color + a large inset box-shadow |
| Print colour adjustment differs | print-color-adjust: exact where colour is meaningful |
scss
// The Chrome autofill fix
input:-webkit-autofill,
input:-webkit-autofill:hover,
input:-webkit-autofill:focus {
-webkit-text-fill-color: var(--av-text-primary);
-webkit-box-shadow: 0 0 0 1000px var(--av-surface-raised) inset;
caret-color: var(--av-text-primary);
transition: background-color 9999s ease-in-out 0s; /* the classic hack */
}iOS Safari specifically
| Quirk | Workaround |
|---|---|
Zooms on focus when font-size < 16px | Inputs are ≥ 16px on touch devices |
| Safe-area insets on notched devices | env(safe-area-inset-*) + viewport-fit=cover |
| Fixed elements jump with the keyboard | visualViewport API in the composer and sticky bars |
| Rubber-band scroll chains to the page | overscroll-behavior: contain |
scss
@media (pointer: coarse) {
.form-control, .form-select { font-size: max(16px, var(--av-font-size-base)); }
}An input under 16px triggers an automatic zoom on iOS that the user then has to undo. This one rule prevents a genuinely annoying bug.
Testing matrix
Automated (Playwright, every PR)
| Project | Engine | Viewport |
|---|---|---|
chromium | Chromium | 1440×900 |
firefox | Gecko | 1440×900 |
webkit | WebKit | 1440×900 |
mobile-chrome | Pixel 8 | 412×915 |
mobile-safari | iPhone 15 | 393×852 |
tablet | iPad Pro 11 | 834×1194 |
js
// playwright.config.js
export default defineConfig({
projects: [
{ name: 'chromium', use: { ...devices['Desktop Chrome'] } },
{ name: 'firefox', use: { ...devices['Desktop Firefox'] } },
{ name: 'webkit', use: { ...devices['Desktop Safari'] } },
{ name: 'mobile-chrome', use: { ...devices['Pixel 7'] } },
{ name: 'mobile-safari', use: { ...devices['iPhone 15'] } },
{ name: 'tablet', use: { ...devices['iPad Pro 11'] } }
]
});Manual (before each release)
| Platform | Browsers |
|---|---|
| Windows 11 | Chrome, Edge, Firefox |
| macOS | Safari, Chrome, Firefox |
| iOS 17+ | Safari, Chrome |
| Android 13+ | Chrome, Samsung Internet |
| Ubuntu | Firefox, Chromium |
Plus: Windows High Contrast, NVDA, JAWS, VoiceOver.
Graceful degradation
If a user arrives on an unsupported browser, the page must still be readable and usable — not blank.
html
<noscript>
<div class="av-banner av-banner--warning">
JavaScript is disabled. Core features still work, but charts, live search, and
drag-and-drop are unavailable.
</div>
</noscript>html
<script>
if (!CSS.supports('color', 'oklch(50% 0.1 180)')) {
document.documentElement.classList.add('av-legacy');
}
</script>scss
// Fallback palette for browsers without oklch()
.av-legacy {
--av-color-primary: #2563eb;
--av-surface-base: #f8fafc;
--av-surface-raised: #ffffff;
--av-text-primary: #0f172a;
/* …a hex mirror of the semantic layer */
}The generated fallback block is emitted automatically by the token build, so it never drifts from the OKLCH source.
Important — do not show a "your browser is not supported" wall. Users of corporate-locked browsers cannot upgrade. Degrade the experience, do not block it.
Version policy
| Event | Action |
|---|---|
| A browser goes out of support upstream | Dropped in the next minor release |
| A new baseline feature reaches all four engines | Adopted in the next minor release |
| Raising the minimum version | Always a major release, announced one release ahead |
We track Baseline and adopt features once they reach "Widely available" (30 months across all engines) unless the feature is progressively enhanceable, in which case we adopt it immediately behind @supports.
Read next: Testing.