At the moment, we advertise Safari as a fully-supported browser. However, we have neither automated nor manual testing on Safari and most developers currently working on XWiki don’t have access to Safari for testing, which makes it also hard to reproduce and fix issues. I propose two changes here:
- Degrade the support status for Safari. As Safari has a significant market share, I’m not suggesting to drop it but we should make it clear that Safari isn’t as well-supported as the other browsers and in particular not regularly tested (but still considered when we evaluate, e.g., if a certain web technology can be used).
- Add automated testing for Safari using BrowserStack. BrowserStack offers free tests for open source and supports integration with Selenium and Jenkins which should allow automated tests using our existing UI tests in Safari on our existing CI system. We would need to verify that this is indeed possible, and that XWiki indeed qualifies for this open source program (I couldn’t find the specific conditions). We also need to check if this could give XWiki committers access to live testing on Safari (and other browsers) to be able to reproduce and fix any identified issues.
I also cannot say how much work the second change is, which might influence if or when we can implement it. Until we implement it or if we don’t implement it, I would propose to clearly state on the browser support page that there is neither manual nor automatic testing performed on Safari.