On Sun, Jul 27, 2014 at 2:25 AM, Krinkle <krinklemail(a)gmail.com> wrote:
Since Grade B never ended up being recognised in any
way by the software,
I've kept that out. And the previously undocumented Grade C represents
browsers we are interested in supporting due to their traffic but only via
the non-javascript mode.
Thanks, Timo - brilliant work as always.
I would like to make a case for moving more browsers into the grade C
category. JavaScript's client-side execution means that being able to
provide predictable user experiences is inherently dependent on client
updates _with reasonable maintenance burden_. By shifting more
browsers into JavaScript-less mode, we accomplish the following:
- Improve performance for low-end users since these JS engines are often slow.
- Significantly reduce the maintenance burden for modern user experience code.
- Reduce risks of security exploits targeting users running an
outdated environment.
We could then also begin to treat JavaScript-less experience as a
first class citizen in support and testing, which helps us serve
low-end users better. If we take the grade C category seriously, we
need to think more about testing these workflows and ensuring we give
the best possible experience to those users.
IMO this should be based on both usage share and maintenance burden
based on developer judgment. IE6-7 would be obvious candidates --
single platform browser, high maintenance burden to test for, etc.
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation