Browsers & Devices

Figuration supports a wide variety of modern browsers and devices, and some older ones. See which exact ones below, as well as detailed information on known quirks and bugs.

Supported Browsers

Figuration supports the latest, stable releases of all major browsers and platforms. On Windows, we support Internet Explorer 11 / Microsoft Edge.

Alternative browsers which use the latest version of WebKit, Blink, or Gecko, whether directly or via the platform's web view API, are not explicitly supported. However, Figuration should (in most cases) display and function correctly in these browsers as well. More specific support information is provided below.

We use Autoprefixer to handle intended browser support via CSS prefixes, which uses Browserslist to manage these browser versions.

You can find our supported range of browsers and their versions in our .browserslistrc:


>= 1%
last 1 major version
not dead
Chrome >= 60
Firefox >= 60
Edge >= 15
Explorer >= 11
iOS >= 10
Safari >= 10
Android >= 6
not ExplorerMobile <= 11

Mobile Devices

Generally speaking, Figuration supports the latest versions of each major platform's default browsers. Note that proxy browsers (such as Opera Mini, Opera Mobile's Turbo mode, UC Browser Mini, Amazon Silk) are not supported.

Chrome Firefox Safari Android Browser & WebView Microsoft Edge
Android Supported Supported N/A v6.0+ Supported
iOS Supported Supported Supported N/A Supported

Desktop Browsers

Similarly, the latest versions of most desktop browsers are supported.

Chrome Firefox Internet Explorer Microsoft Edge Opera Safari
Mac Supported Supported N/A Supported Supported Supported
Windows Supported Supported Supported, IE11+ Supported Supported Not supported

For Firefox, in addition to the latest normal stable release, we also support the latest Extended Support Release (ESR) version of Firefox.

Unofficially, Figuration should look and behave well enough in Chromium and Chrome for Linux, and Firefox for Linux, though they are not officially supported.

Internet Explorer

Internet Explorer 11+ is also supported, IE 10 and down are not. Please be aware that some CSS3 properties and HTML5 elements are not fully supported in Internet Explorer, or require prefixed properties for full functionality. Visit Can I useā€¦ for details on browser support of CSS3 and HTML5 features.


Some of Figuration's JavaScript Widgets have some support for the use of MutationObserver to watch for and respond to changes in the DOM.

Modals and Dropdowns on Mobile

Overflow and Scrolling

Support for overflow: hidden; on the <body> element is quite limited in iOS and Android. To that end, when you scroll past the top or bottom of a modal in either of those devices' browsers, the <body> content will begin to scroll. See Chrome bug #175502 (fixed in Chrome v40) and WebKit bug #153852.

iOS Text Fields and Scrolling

As of iOS 9.2, while a modal is open, if the initial touch of a scroll gesture is within the boundary of a textual <input> or a <textarea>, the <body> content underneath the modal will be scrolled instead of the modal itself. See WebKit bug #153856.

Browser Zooming

Page zooming inevitably presents rendering artifacts in some components, both in Figuration and the rest of the web. Depending on the issue, we may be able to fix it (search first and then open an issue if need be). However, we tend to ignore these as they often have no direct solution other than hacky workarounds.


Even in some modern browsers, printing can be quirky.

As of Safari v8.0, use of the fixed-width .container class can cause Safari to use an unusually small font size when printing. See Bootstrap issue #14868 and WebKit bug #138192 for more details. One potential workaround is the following CSS:

@media print {
.container {
width: auto;


In order to provide the best possible experience to old and buggy browsers, Figuration uses CSS browser hacks in several places to target special CSS to certain browser versions in order to work around bugs in the browsers themselves. These hacks understandably cause CSS validators to complain that they are invalid. In a couple places, we also use bleeding-edge CSS features that aren't yet fully standardized, but these are used purely for progressive enhancement.

These validation warnings don't matter in practice since the non-hacky portion of our CSS does fully validate and the hacky portions don't interfere with the proper functioning of the non-hacky portion, hence why we deliberately ignore these particular warnings.