Browser Support
Decision Process
The decision process occurs every 6 months and determines the minimum set of browser versions to test.
- 1Align with CoE Architecture, UX, Security, Marketing and Business
- 2Presented on the UX Community
- 3MT (Tom Wouters): Presented & final decision
- 4Communication on UX Community & Yammer
Important because
- Cost reduction (INT)
- Security (EXT)
- User eXperience (EXT)
- Digital channels....
Ownership
- UX Central
- process to be finetuned further
Hot topics
- Microsoft Internet Explorer 11
- Microsoft Edge Chromium
Up to the front door
Authentication works
Application opens without problems
 |  |  |  |  |  |
| Chrome | Edge Chromium | Safari | Firefox | Internet Explorer | Edge (legacy) |
explanation
- Active support
- All products squads should test upfront 'up to the frontdoor'
Internal - Beyond front door
| | | | | | ||
| Chrome | Edge Chromium | Safari | Firefox | Internet Explorer | Edge (legacy) | ||
Desktop | |||||||
| - | |||||||
Mobile | - | - | - | ||||
| - | - |
- Active support
- These browsers are tested upfront
- Only the most recent major version
- Reactive support
- No upfront testing needed
- We'll solve problems (best effort) for versions < 6m old
- Remarks
- Mobile browsers: should be tested only actively for applications targeting smartphone users
- Chrome,Firefox and Safari: additional security warnings are shown for version older than the current and previous major release
External communication
| | | | | | ||
| Chrome | Edge Chromium | Safari | Firefox | Internet Explorer | Edge (legacy) | ||
Desktop | |||||||
| - | |||||||
Mobile | - | - | - | ||||
| - | - |
explanation
- We name it
- This the so called Browser support matrix
- Active support
- For end-user documentation ther is no difference between active and reactive support
- We keep the version limit < 6 months old