Browser and device compatibility
What browsers, mobile phones, tablet, and ponies you need to support
For browser support, aim for content and functionality to be unobstructed on browsers released within the last five years and have JavaScript enabled; this is represents virtually all users of the EMBL-EBI site (in excess of 99.9%).
As a guiding rule, test for compatibility on any browser or device that represents more than 2% of the usage of www.ebi.ac.uk.
As intended by the CSS specification, not all browsers, devices, or users render content to look exactly the same. Our aim is to create an accessible and visually consistent design across a broad range of clients, not pixel-prefect designs. Further, we build atop the basic functionality, adding progressive-enhancement features to newer classes of browsers and devices.
How to use this
The below describes how the EMBL-EBI Web Development team analyses and supports the EBI Framework and sites the team maintains, we suggest you use this as a starting point, adapting it for the browsers of your users, and devices you can procure to test on.
For further guidance, reach out to the Web Development team for assistance on how to set up a testing environment.
As of this writing (21/10/2015), currently supported desktop browsers and their usage:
Browser | Version(s) | Traffic % |
---|---|---|
Chrome | 46, 45, 44 | 40.0% |
Firefox | 40, 39, 38 | 18.6 |
Safari | 9, 8, 7.1 | 8.0 |
IE | 12, 11 | 6.6 |
Mobile and tablet support
The mobile and tablet space is highly fragmented with reliable guarantees of support often hard to offer as device maker, browser, and OS version are each a variable in HTML/CSS rendering.
With this in mind, there are three classes of mobile and tablet support:
- Primary support
- These devices represent a greater than 5% share of mobile traffic and the Web Dev team posses these devices to test against. Testing will be performed proactively for each major release (qualified as 0.1 increment in versioning, or greater).
- Best effort
- These devices represent a greater than 2.5% share of mobile traffic, and/or the Web Dev team does not have a device to test against. The Web Dev team will attempt to support these users but without physical devices to test against, cannot guarantee ongoing compatibility.
- Where available, simulator/emulator tools will be used to test against during each major release
- Bug reports from users will be addressed, and documented in hopes of ensuring no degradation in future updates
- Legacy
- Devices that represent less than 2.5% of mobile traffic and are on the decline month-over-month.
- The Web Dev team does not thoroughly test against physical devices or emulated software
- The team will address user bug reports will be addressed, attempting a fix where it does not adversely affect performance or Best effort/Primary support devices
Current classifications
A synopsis of the ecosystem as of September 2015. This is targeted for a twice annual update, the classification of devices is subject to change if a high need browser or device is identified.
OS | Traffic | Support level |
---|---|---|
Android 4.x | 43.5% | Primary support |
Android 5.x | 20.4 | Primary support |
iOS 9.x | 9.5 | Primary support |
iOS 8.x | 8.1 | Primary support |
Android 2.x | 3.1 | Best effort |
Windows Phone | 2.8 | Best effort |
Browser | Traffic | Support level |
---|---|---|
Safari | 40.1% | Primary support |
Chrome | 30.7 | Primary support |
Android | 9 | Primary support |
IE 11 | 6.7 | Best effort |
UC Browser | 5.1 | Best effort |
Chrome iOS | 2.7 | Best effort |
Note on tablets: Currently all tablet devices are limited to best effort, as they represent less than 2.5% of traffic (currently at 1.8%).
Special targets
These devices, browsers, or OS versions have been identified as critical needs.
None currently known.
Have a use case that's not covered?
Please open an issue in the tracker. We'll update this living pattern library with your feedback.