Skip to the content

Browser Support

Apollion supports every browser in Baseline 2024: the engine versions that ship all web-platform features that became available across Chrome, Edge, Firefox and Safari during 2024. Mobile browsers are first-class — the design system is mobile-first, so iOS Safari and Chrome for Android are part of the contract, not an afterthought.
Guides

Supported browsers

Browser
Minimum version
Chrome (desktop)
130
Edge
130
Firefox (desktop)
132
Safari (macOS)
18.2
Safari on iOS / iPadOS
18.2
Chrome for Android
130
Android WebView
130
Firefox for Android
132
Samsung Internet
28
Opera
115
Scrolls sideways inside the table. The page does not.

The same list ships in the package as its browserslist field, so tools that read it (bundlers, CSS post-processors, linters) see the floor Apollion was built against.

Support levels

Not every CSS feature is equal. Apollion classifies each one before it lands in a component:

Level
What it means for you
Supported
Works the same in every browser above. Every documented behavior is a guarantee here.
Enhanced where supported
Newer engines get extra polish (a smoother transition, a native control); every supported browser keeps the same function. Documentation always marks these as where supported — never a promise.
Not used
Features available in a single engine only are never relied on, however attractive.
Scrolls sideways inside the table. The page does not.

Enhancements shipping today:

  • View transitions — the opt-in viewTransitionStyles wiring animates state changes where the View Transitions API exists; elsewhere the change is instant.
  • Static Sheet — trigger buttons use native Invoker Commands (command/commandfor) and the dialog uses closedby where available; SheetScript supplies the same open/close behavior everywhere else.
  • TextArea autoResize — the field grows with its content through field-sizing where supported; elsewhere it keeps the fixed height set by rows.
  • Accordion motion — panels expand and collapse with a transition through ::details-content where supported; elsewhere they open and close instantly. Opening, closing and one-open-at-a-time work in every supported browser (native <details name>).

Older browsers

Versions older than the table are not tested and not supported. The published build targets ES2018, so pages usually still render, but expect gaps: enter animations may be missing and color-mode switching relies on light-dark(). If you must serve older engines, link the tokens CSS surface (output.cssModes) for colors — it switches modes through plain custom properties.

How support is verified

  • Every story is screenshot-tested in current Chromium, Firefox and WebKit engines, plus dark mode and a 390 px mobile viewport.
  • A feature enters the Supported level only when every browser in the table ships it; anything newer goes through Enhanced where supported with a working fallback.
  • The floor moves only on purpose: it is pinned to a Baseline year, never a rolling query, and each change is announced in the changelog.

Aligning your app

Declare the same floor in your application so your own build tools agree with Apollion's. Recent browserslist versions accept the Baseline query directly:

{
  "browserslist": ["baseline 2024 with downstream"]
}

Or copy the explicit list from @apollion-dsi/core's package.json.

See also