Device / Browser Coverage

[therebelrobot]

Which browsers should we support in our code, which devices, etc. In reference to #89 . A short list we would need to decide coverage for would include

• Browsers
  • IE (6, 7, 8, 9, 10, 11)
  • Spartan (when available)
  • Firefox (and how many versions back)
  • Opera (and how many versions back)
  • Chrome (I think this is a given, but also how many versions back)
• Platforms
  • iOS - (browsers, versions and which devices)
  • Android - (browsers, versions and which devices)
  • Windows
  • Mac
  • Linux

WG: feel free to comment below or edit this thread with a 👍 or 👎 for voting

We should also document somewhere in our website docs the final list we decide on, so we can have a standards system set up (no merge accepted without proper cross-browser support, etc.)

[Fishrock123]

I don't really care about browsers <IE9 and <Android4.4

(Stock android browser(s) pre-4.4 / chrome are basically broken)

Generally, if caniuse looks anything like this and it significantly cuts your dev hassle, it's probably worth using imo. (Unless you are specifically dealing with people who don't even know other browsers exist.)

(Edit: Anything "evergreen" is good.)

[mikeal]

The website should support at least the same range of browsers that appear by default on the io.js supported operating systems.

[therebelrobot]

+1 @mikeal

[snostorm]

I think we should have things still work on simple browsers for sure. But our standards for design and appearance should follow suit and just remain as simple for these users. (If we structure the DOM and base classes right in our templates we should be able to have it degrade well.)

The recent PR on this depended a little too much on design parity, which is why I down voted it, although more can be done in the structure of DOM layout, etc. to have it progressively simplify better.

Since io.js does run on some pretty limited devices it is a nice touch to make sure people can, at minimum, easily download, reference the APIs, changelogs, etc. even if not using the same UI flare/JS we might later add to make experiences like navigating through said docs easier.

[arthurvr]

IE (6, 7, 8, 9, 10, 11)

I work on quite a bunch of development focused sites and I know none of them who has more then 3% older then IE10. Not worth it IMHO.

(and how many versions back)

For all evergreen browsers we should just support 1 version back.

[Fishrock123]

We have inadvertently come to support anything that supports flexbox, perhaps somewhat unfortunately. Mostly because it just takes way less time and fidgeting to set up.