Table of Contents

Swift Requirements

Supported browsers

DynamicWeb Swift supports the latest, stable releases of all major browsers and platforms.

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, Swift should (in most cases) display and function correctly in these browsers as well. More specific support information is provided below.

  • Latest 2 major versions of the following browsers:
    • Chrome
    • Safari
    • Firefox
    • Edge

We use Autoprefixer to handle intended browser support via CSS prefixes, which uses Browserslist to manage these browser versions. Consult their documentation for how to integrate these tools into your projects.

Swift utilizes modern CSS features – features that are reported as widely supported by https://caniuse.com/ can be used in Swift. Some older browsers might not, or only partially, support some of these CSS features and might not render as expected in these cases.

Mobile devices

Generally speaking, Swift 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 Supported Supported
iOS Supported Supported Supported

Desktop browsers

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

Chrome Firefox Microsoft Edge Safari
Mac Supported Supported Supported Supported
Windows Supported Supported Supported

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

Responsive and adaptive behaviour

Swift can be setup up to either use Adaptive or Responsive rendering in mobile devices.

The desktop viewport is used from ≥992px and mobile below that threshold when using responsive rendering.

When using adaptive rendering, the browser UserAgent is used to detect mobile/tablet or desktop devices and render either the mobile or desktop view accordingly. Read more about how DynamicWeb handles device detection here.

Adaptive rendering is default because it is faster than responsive rendering.

When in adaptive rendering, resizing the browser window will not change to mobile view. Then the browser developer tools must be used to shift to mobile view and reload the page.

If shifting to mobile view automatically when resizing browser window is required, Responsive setting must be activated.

HTML and CSS validation

Swift is made using HTML 5 and CSS 3.

Markup must be validated against https://validator.w3.org/ - errors are not accepted but warnings can be ok. Errors on semantics are accepted though.

Some errors and warnings are related to missing content – i.e. missing Alt texts can be due to missing filling out fields in the backend and needs to be fixed by adding the missing required content in the backend.

Internet Explorer

Internet Explorer is not supported.

iPad Pro

Since Apple have decided that iPad pro using iOS 12+ should behave like a desktop browser, iPad pro is supported as a desktop browser.

DynamicWeb uses UserAgent detection to shift between mobile and desktop mode when using adaptive rendering.

iPad Pro identifies itself as a desktop computer and therefore Swift will render like the desktop version.

Shifting to Responsive rendering instead of Adaptive rendering can in some cases handle that iPad pro renders in mobile view when in vertical mode but will render in desktop mode when in horizontal view. This depends on the screen resolution of the device as per Swifts viewport breakpoints.

It is possible to detect iPad pro using JavaScript in the browser and reload the page in mobile version – this is not part of Swift and must be implemented in the project as a custom modification if required. Check out our client-side workaround for iPad detection here.

To top