e-satisfaction

Browser and OS compatibility

Collection is built in standard JavaScript and aims to run everywhere your customers do. It's tested and verified against current desktop and mobile platforms, and it's designed to degrade gracefully rather than break a page when it meets something older.

The guiding rule: if a browser still receives security updates from its vendor, collection is meant to work on it. The current and previous major versions of the evergreen browsers (Chrome, Edge, Firefox, Safari) are actively tested; the tables below list the verified baseline alongside the modern platforms collection runs on today. They're representative rather than exhaustive — any device with a current evergreen browser is supported even if it isn't named.

Operating systems

Operating systemStatus
Windows 11Supported
Windows 10Supported
Windows 7, 8, 8.1Supported (legacy)
Windows Vista, XP and earlierNot tested
macOS 11 (Big Sur) and laterSupported
macOS 10.11–10.15Supported
macOS 10.10 (Yosemite) and earlierNot tested
ChromeOSSupported
Linux (Ubuntu, Debian, Fedora) with Chrome or FirefoxSupported
Other / older Linux distributionsNot tested

Desktop browsers

Evergreen browsers update themselves, so the minimum version is a floor, not a ceiling — keep the browser current and you're covered.

BrowserMinimum versionStatus
Google Chrome64Supported
Mozilla Firefox60Supported
Microsoft Edge (Chromium)79Supported
Apple Safari11Supported
Opera51Supported
Microsoft Edge (legacy EdgeHTML)42Supported (legacy)
Internet ExplorerNot supported

Mobile browsers and devices

On mobile, current versions of Safari on iOS/iPadOS, Chrome on Android, Samsung Internet and Firefox for mobile are supported. The table below lists verified devices with their portrait viewport size (CSS pixels, width × height); newer devices with the same engines are supported too.

DeviceViewport (portrait, W × H)Status
iPhone 4320 × 480Supported
iPhone 5 / SE (1st gen)320 × 568Supported
iPhone 6 / 7 / 8 / SE (2nd–3rd gen)375 × 667Supported
iPhone 6 / 7 / 8 Plus414 × 736Supported
iPhone X / XS / 11 Pro375 × 812Supported
iPhone XR / 11414 × 896Supported
iPhone 12 / 13 / 14390 × 844Supported
iPhone 12–13 Pro Max / 14 Plus428 × 926Supported
iPhone 14 Pro / 15 / 16393 × 852Supported
iPhone 15 Plus / 15 Pro Max / 16 Plus430 × 932Supported
Samsung Galaxy S7 / Note 3360 × 640Supported
Samsung Galaxy S8 / S9360 × 740Supported
Samsung Galaxy S20 / S21 / S22360 × 800Supported
Samsung Galaxy S23 / S24360 × 780Supported
Samsung Galaxy S24 Ultra384 × 824Supported
Google Pixel 5393 × 851Supported
Google Pixel 6 / 7 / 8412 × 915Supported
iPad mini (older)768 × 1024Supported
iPad mini (6th gen)744 × 1133Supported
iPad 10.9" / iPad Air820 × 1180Supported
iPad Pro 11"834 × 1194Supported
iPad Pro 12.9"1024 × 1366Supported

How the snippet stays compatible

The standard snippet loads a build that suits the page automatically — it serves a jQuery-free bundle when no jQuery is present, and a jQuery-aware bundle when one is. The script is loaded asynchronously and attaches on load, so it never blocks your page from rendering, and it falls back quietly on environments it can't fully support.

A note on layout, not support

Whether the widget fits a given screen is about display settings, not browser support. Widget type, position and mobile behaviour are configured on the Web integration page — see override web display settings to vary them per page.

If the widget doesn't show

If a survey doesn't render on a particular browser or device, it's usually a configuration or page-environment issue rather than a compatibility gap. Work through Troubleshooting first — it covers content-security policies, cookie-consent gating, duplicate snippets and the other common causes.

If you've ruled those out and believe it's a genuine compatibility problem on a current browser or OS, contact support with the browser, version and operating system so the team can reproduce it and either fix it or update this guidance.