On 11/20/2012 05:19 PM, James Forrester wrote:
* Desktop: Current and immediately-previous versions
of Chrome, Firefox,
MSIE and Safari
* Tablet: Current versions of iOS/Safari; Current and immediately-previous
ones of Android
* Mobile: Current versions of iOS/Safari; Current and the five previous
ones of Android[*]
Anything not in this list may "happen to work" but WMF Engineering will not
spend resources (read, developer time) on it.
What types of problems are giving you a hard time keeping the support?
Newest versions of browsers can be as painful to support as legacy ones,
but the types of problems are probably very different.
Are we talking about bugs in the browsers? Sui generis interpretations
of HTML/CSS/JS specs? Performance problems? Limitations in the devices
using those browsers? Use of browser X specific features / workarounds
in our software?
Or is it simply a matter of us being unable to test through >15 browsers
and therefore trying to find criteria to limit the number to a more
feasible <10?
Someting to take into account is that developer teams of browsers not in
Wikimedia's "Tier 1" might be interested in driving the tests
themselves, as part of their productization work. Think of Opera,
Windows Phone, Blackberry, Series 40... Wikipedia is a top global site
and probably they are already testing their latest version against it.
We could guide them better on what to test and how to find / file /
comment on bugs and contribute patches. Having a regular contact in each
of those teams would be really useful.
Would this be helpful, and fitting in your browser support plans?
--
Quim