Closed
Bug 939994
Opened 11 years ago
Closed 8 years ago
Document the browser support matrix
Categories
(L20n :: JS Library, defect, P2)
L20n
JS Library
Tracking
(Not tracked)
RESOLVED
FIXED
1.0
People
(Reporter: mgol, Assigned: stas)
Details
It seems a browser support matrix is nowhere to be found on both http://l20n.org and https://github.com/l20n/l20n.js/. It is very important for web developers which browsers are supported before diving into a library. This info should be made public & official and be easily accessible.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → stas
Priority: -- → P2
Target Milestone: --- → 1.0
Assignee | ||
Comment 1•9 years ago
|
||
Here's my proposal for the webcompat version: Firefox: 32+ (September 2014; navigator.languages first appeared in 32) Chrome: 38+ (October 2014; Map and Set et al. are introduced) Safari: 8+ (June 2014, part of Yosemite) IE: 11 & Edge
Reporter | ||
Comment 2•9 years ago
|
||
Sounds good except I don't think it makes sense to officially support unsupported Firefox/Chrome versions; you'd have to have them in CI to be able to claim full support. Rolling-release browsers update themselves quickly so it's not worth reaching into the past. See what jQuery does in this regard: http://jquery.com/browser-support/ IMO it makes sense to say: Firefox: current & previous stable, current & previous ESR Chrome: current & previous stable Edge: current & previous stable Safari: 8+ IE: 11
Comment 3•9 years ago
|
||
I like :m_gol's version better, except that I don't think it makes sense to support Safari 8 anymore. I'd set 9 as a minimum version.
Assignee | ||
Comment 4•9 years ago
|
||
It looks like we're converging on the final set. Good :) Here's a new version of the proposal: Firefox: current & previous stable, current & previous ESR Chrome: current & previous stable Edge: current & previous stable Safari: 9 IE: 11 Re. "previous ESR" for Firefox: currently that's version 31 which doesn't have navigator.languages. However, since we need to fall back on [navigator.language] for IE11 anyways, I think that's fine. Zibi, Michał -- thoughts?
Flags: needinfo?(m.goleb+mozilla)
Flags: needinfo?(gandalf)
Reporter | ||
Comment 5•9 years ago
|
||
(In reply to Staś Małolepszy :stas from comment #4) > It looks like we're converging on the final set. Good :) > > Here's a new version of the proposal: > > Firefox: current & previous stable, current & previous ESR > Chrome: current & previous stable > Edge: current & previous stable > Safari: 9 > IE: 11 > > Re. "previous ESR" for Firefox: currently that's version 31 which doesn't > have navigator.languages. However, since we need to fall back on > [navigator.language] for IE11 anyways, I think that's fine. > > Zibi, Michał -- thoughts? Sounds good (more or less) for desktop browsers, I think we should assert mobile support as well, though. iOS differs slightly from desktop Safari in a number of way, same for Chrome for Android, maybe Firefox for Android as well? One remark - wouldn't it be better to not support last 2 Fx ESRs but only those supported by Mozilla? Sometimes it's last 2 of them but most of the time one (since there's a two-version overlap). I guess it might be harder to configure it that way and not think about it, though.
Flags: needinfo?(m.goleb+mozilla)
Comment 6•8 years ago
|
||
We now have a formal list of supported environments: https://github.com/l20n/l20n.js/blob/master/docs/compat.md Reopen if needed.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(gandalf)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•