Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define specific browser support guidelines #9301

Open
aweary opened this issue Mar 31, 2017 · 11 comments
Open

Define specific browser support guidelines #9301

aweary opened this issue Mar 31, 2017 · 11 comments

Comments

@aweary
Copy link
Contributor

aweary commented Mar 31, 2017

As it stands the only real solid guideline we have for browser support is that we support IE9+. But there are so many other outdated browser versions that are unreasonable to support or worry about.

It would be useful if we had more specific guidelines on what browsers we should target. Does Safari on iOS 3 matter? FireFox 4? You get the idea.

If we had a well-documented range of browser version that we know should work it would make it a lot easier to run through our DOM fixtures in BrowserStack and know we're safe.

Maybe the internal core team can work internally with analytics to see what browsers Facebook needs to support and work forward from there?

cc @gaearon @nhunzaker

@nhunzaker
Copy link
Contributor

nhunzaker commented Mar 31, 2017

I like the idea of getting a browser list from Facebook.

Additionally, we've recently sent out a couple of PRs removing legacy IE8 code, but there's still quite a bit left:

@nhunzaker
Copy link
Contributor

Another useful chart:
http://caniuse.com/usage-table

@sophiebits
Copy link
Contributor

I will try to write something up for this next week. Bug me incessantly in a week if I've forgotten please.

@ghost
Copy link

ghost commented Apr 1, 2017

@spicyj , you could self-assign this issue to you, and then make it a habit to check https://github.com/issues/assigned for things you've forgotten. Just a suggestion.

@aweary
Copy link
Contributor Author

aweary commented Apr 10, 2017

@spicyj the incessant bugging is slated to begin at any moment 😄

@sophiebits
Copy link
Contributor

okay can't wait

@aweary
Copy link
Contributor Author

aweary commented Apr 13, 2017

@spicyj 🐛

@sophiebits
Copy link
Contributor

Sorry, maybe next week. :(

@blling
Copy link

blling commented Sep 27, 2017

Any final plan?

@sophiebits
Copy link
Contributor

sophiebits commented Oct 4, 2017

Here's my thinking based on checking some browser stats. It doesn't provide a full list but at least provides a list of some browsers that we definitely need to support. For things not on this list, we'll need to discuss more but I'm hoping this list can at least be helpful as a baseline.

Definitely supported with full support:
Chrome 49 (last available on XP/Vista)
Firefox ESR
IE 11
Safari 10
Edge 14

Probably supported with full support:
Safari 7
Chrome 41 (seeing a bunch of traffic here on Windows 7, not sure why)

Probably OK not to support:
Safari 6
IE9 (not 100% sure on this)

Definitely not supported (would be nice to enumerate what this means. should anything work?):
IE8

@nhunzaker
Copy link
Contributor

For determining the current Firefox ESR, I found this downloads page helpful:
https://www.mozilla.org/en-US/firefox/organizations/all/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants