Skip to main content

Supported browsers

Anna Dziurosz avatar
Written by Anna Dziurosz
Updated this week

Moss supports modern desktop web browsers that are compatible with Baseline web.dev “widely available” web platform features.

These features are defined and tracked by the W3C Web Platform DX (WebDX) Community Group. They represent web platform functionality that has been supported by all major browsers for a sustained period, making them a stable foundation for modern web applications.

In short:

  • If a desktop browser version supports the widely available baseline, it is considered supported by Moss.

  • Mobile browsers are not officially supported. Core flows may work, but mobile is outside our compatibility guarantees.


Currently supported browser versions

The table below reflects the current “widely available” core browser set.

Browser

Minimal supported version

Release date

Chrome

115

2023-07-21

Microsoft Edge

115

2023-07-21

Firefox

116

2023-08-01

Safari (macOS)

16.4

2023-04-11

Opera

101

2023-07-26

Notes

  • Chromium-based browsers (e.g. Opera) follow the Chrome baseline.

  • Internet Explorer (including IE11) and discontinued browsers are not supported.

  • Moss explicitly recommends Chrome, Edge, and Firefox on desktop for the best experience.


How to check supported browsers

The up-to-date browser list for the widely available baseline can be found here:
Supported browsers

If a desktop browser version appears in the core browser set on that page, it is compatible with the baseline Moss relies on and is therefore supported.


Why we use the “widely available” baseline

The widely available baseline is a community standard maintained by the W3C Web Platform DX (WebDX) Community Group.

A web feature becomes widely available when:

  • it is implemented by all core browsers (Chrome, Edge, Firefox, Safari), and

  • it has been supported across those browsers for at least 30 months.

This approach gives Moss:

  • a stable and predictable compatibility target,

  • alignment with industry standards, rather than a custom Moss-only definition,

  • freedom to use modern Web APIs and CSS without excessive polyfills,

  • a clear and defensible answer for customers and support teams.


Did this answer your question?