Skip to content

Browser Support ​


Support matrix ​

BrowserMinimumRationale
Chrome / Edge111oklch(), cascade layers, container queries
Firefox113oklch()
Safari (macOS)16.4Container queries, oklch()
Safari (iOS)16.4Same
Opera97Chromium 111
Samsung Internet23Chromium 111
Chrome Android111
Firefox Android113

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 all

Not supported ​

BrowserReason
Internet Explorer (any)Discontinued June 2022. No custom properties, no grid support worth having.
Legacy Edge (≤ 18)Discontinued March 2021
Safari ≤ 16.3No container queries
Chrome ≤ 110No oklch()
Opera MiniNo JavaScript execution in extreme mode
Any browser without CSS Custom PropertiesThe 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 with container-query-polyfill, and flattens cascade layers. It is 34% larger and loses runtime theming.


Required platform features ​

CSS ​

FeatureChromeFirefoxSafariUsed for
Custom properties49319.1Everything
@layer999715.4Cascade control
oklch()11111315.4Colour system
Container queries10511016.0Component responsiveness
:has()10512115.4Selection states
Logical properties896615.0RTL
inset shorthand876614.1Positioning
aspect-ratio888915.0Media
gap in flexbox846314.1Layout
color-scheme819613Native dark UI
content-visibility8512518Long lists (progressive)
text-wrap: balance11412117.5Headings (progressive)
@view-transition126—18Page transitions (progressive)

The last four are progressive enhancements — the interface works without them.

JavaScript ​

FeatureUsed for
ES modules + dynamic import()Code splitting
ProxyReactive store
WeakMapInstance registry
AbortController / AbortSignalListener cleanup
IntersectionObserverLazy init, scroll reveal, scrollspy
ResizeObserverChart and grid resizing
MutationObserverDynamic markup init
CustomEventDOM event bridge
structuredCloneStore snapshots
Optional chaining / nullish coalescingEverywhere
Private class fieldsCore 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 ​

QuirkWorkaround
100vh includes collapsing toolbar chromeUse 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 limitedFlatpickr for consistent appearance
overflow: hidden on <body> does not always lock scroll on iOSposition: fixed scroll lock in the modal module
Smooth scrolling ignores scroll-padding in some versionsscrollIntoView({ block: 'center' })
Momentum scroll fires no scroll events until it settlesTopbar auto-hide uses a threshold

Firefox ​

QuirkWorkaround
No ::-webkit-scrollbarscrollbar-width / scrollbar-color used first
:has() only from 121Guarded with @supports selector(:has(*))
Different default focus ringOverridden globally
<input type="number"> spinner styling differsWe avoid type="number" for most fields anyway

Chrome / Edge ​

QuirkWorkaround
Autofill background cannot be changed-webkit-text-fill-color + a large inset box-shadow
Print colour adjustment differsprint-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 ​

QuirkWorkaround
Zooms on focus when font-size < 16pxInputs are ≥ 16px on touch devices
Safe-area insets on notched devicesenv(safe-area-inset-*) + viewport-fit=cover
Fixed elements jump with the keyboardvisualViewport API in the composer and sticky bars
Rubber-band scroll chains to the pageoverscroll-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) ​

ProjectEngineViewport
chromiumChromium1440×900
firefoxGecko1440×900
webkitWebKit1440×900
mobile-chromePixel 8412×915
mobile-safariiPhone 15393×852
tabletiPad Pro 11834×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) ​

PlatformBrowsers
Windows 11Chrome, Edge, Firefox
macOSSafari, Chrome, Firefox
iOS 17+Safari, Chrome
Android 13+Chrome, Samsung Internet
UbuntuFirefox, 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 ​

EventAction
A browser goes out of support upstreamDropped in the next minor release
A new baseline feature reaches all four enginesAdopted in the next minor release
Raising the minimum versionAlways 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.

Documentation for @creativeigniter/adminvora