-
Notifications
You must be signed in to change notification settings - Fork 46.9k
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
Comments
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:
|
Another useful chart: |
I will try to write something up for this next week. Bug me incessantly in a week if I've forgotten please. |
@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. |
@spicyj the incessant bugging is slated to begin at any moment 😄 |
okay can't wait |
@spicyj 🐛 |
Sorry, maybe next week. :( |
Any final plan? |
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: Probably supported with full support: Probably OK not to support: Definitely not supported (would be nice to enumerate what this means. should anything work?): |
For determining the current Firefox ESR, I found this downloads page helpful: |
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
The text was updated successfully, but these errors were encountered: