Browser support
Semetrika targets evergreen browsers - the current and previous stable release of Chrome, Firefox, Safari, and Edge. No polyfills are shipped. If your consumer base needs older browsers, you are responsible for any polyfilling, fallbacks, or graceful degradation.
Version floor
The hard floor is set by the CSS features Semetrika uses unmodified - it is not driven by the JavaScript target. The most modern feature in Semetrika's CSS is :has(), which became universally available in Firefox 121 (December 2023). That date sets the practical floor:
| Browser | Minimum version | Released |
|---|---|---|
| Chrome | 105 | Aug 2022 |
| Edge (Chromium) | 105 | Aug 2022 |
| Firefox | 121 | Dec 2023 |
| Safari (macOS, iOS) | 15.4 | Mar 2022 |
| Opera | 91 | Sep 2022 |
| Samsung Internet | 21 | Oct 2023 |
Browsers older than the floor will load and parse the bundle, but selectors that use :has() will simply not match, so the affected styles will not apply. The page will render - it will not be styled to the design system's intent.
Required CSS features
| Feature | What it enables in Semetrika |
|---|---|
:has() | Parent-aware styling - cards with a header, forms with an error, sections that contain a sticky element. |
| Custom properties | The entire token system. var(--token) is everywhere. |
| CSS Nesting | Used in source CSS; LightningCSS flattens for the shipped bundle, so the compiled bundle does not require nesting. |
@container queries | Component reactions to their container size. Used by carousel, drawer, and the options system. |
| Flexbox | Layout primitives. Modern syntax (flex, gap, justify-content, align-items). |
| Grid | The 12-column grid utility, plus a few component-internal grids (deflist, footer). |
| Logical properties | margin-inline, padding-block, inset-inline-start. Direction-aware - works in both LTR and RTL contexts. |
oklch() color space | Used by the palette generator and some semantic tokens; falls back to RGB representation when not supported by browser. |
prefers-color-scheme | Optional dark-scheme auto-detection at the consumer level. See Color schemes. |
prefers-reduced-motion | Automatic --option-animations: 0 when the OS preference is set. See Tokens. |
JavaScript target
The shipped semetrika.min.js bundle is compiled to ES2020 by esbuild. Practically:
| Feature | Available in ES2020 |
|---|---|
let, const, arrow functions | Yes |
class, async / await | Yes |
| Spread, rest, destructuring | Yes |
Optional chaining (?.) | Yes |
Nullish coalescing (??) | Yes |
Dynamic import() | Yes |
BigInt | Yes |
Private class fields (#name) | No - transformed |
The CSS floor (Firefox 121, Safari 15.4) is well above ES2020 support, so the JS bundle works on every browser that can render Semetrika's CSS.
No polyfills shipped
Semetrika does not bundle a polyfill for :has(), @container, custom properties, or anything else. Reasons:
- Polyfills bloat the bundle for the >99% of users who do not need them.
- Polyfills for modern CSS features (
:has(), container queries) are not reliable - they cannot fully replicate the native behavior and introduce subtle bugs. - The floor is already deep enough (every browser version from 2022-2023) that most consumer bases are well above it.
If you need to support browsers below the floor, polyfill at the consumer level - load the polyfills you actually need, conditionally, and ship them with your own bundle.
Mobile and embedded
iOS Safari shares the WebKit engine with macOS Safari and follows the same version floor. Embedded WebViews on iOS that are pinned to an older WebKit (Cordova / Capacitor apps that have not been re-built recently) may be below the floor.
Android WebView follows Chrome's release cadence; current Android devices are well above the floor.
Server-side rendered HTML (SSR / SSG) is unaffected - the HTML Semetrika encourages you to write is plain semantic HTML that any browser can render. The CSS modernity question only affects how the page looks, not whether it loads.
What "evergreen" means here
"Evergreen" means the browser auto-updates and users are typically on the current or previous stable release within weeks of a new version. Chrome, Edge, Firefox, Safari, and Opera are all evergreen on modern desktop and mobile platforms.
Browsers that are intentionally not evergreen - Internet Explorer (retired), pre-Chromium Edge (retired), legacy embedded WebViews on long-tail devices - are not supported. The combined market share of these browsers is below the threshold where polyfilling becomes worthwhile, and the cost of supporting them is a bigger, slower, more bug-prone bundle for everyone else.
Reporting an issue
If you observe broken styling or behavior on a browser within the supported floor, please open an issue with the browser name, version, and a reduced reproduction (a CodePen or a static HTML snippet). Issues on browsers below the floor will be closed as out-of-scope.