Browser support
The styleguide’s CSS targets current browsers. Hosts that must still run on Chrome 120, such as retailer screens, use the compat build instead.
Which browsers count as current comes from real traffic — see the Browser support matrix.
Chrome 120
Section titled “Chrome 120”@tmedxp/styleguide/compat/*.css supports the whole styleguide on Chrome 120. It carries the same styles as the main build, with the syntax lowered so Chrome 120 can parse it.
Supported means every component, layout and utility renders, is usable and keeps a stable layout. It does not mean pixel-identical to current Chrome: features Chrome 120 lacks degrade as listed below. The claim covers the CSS only, not React components.
Known degradations
Section titled “Known degradations”- The accordion opens and closes without animation. Its spacing is unaffected.
- Size changes that animate to or from
autosnap instead. - Scrollbars styled by the overflow utilities fall back to the platform scrollbar.
- Text box trimming is ignored, so text keeps its full line height and can sit a pixel or two off-centre.
Not supported
Section titled “Not supported”A component that can’t degrade acceptably is listed here as not supported on Chrome 120, announced in the changelog. None is today.
How we know
Section titled “How we know”Every build checks the styleguide’s CSS against Chrome 120’s feature support. Each gap it finds is either fixed with a fallback or listed above as a known degradation. The styleguide is not yet rendered in a real Chrome 120 or on retailer hardware.