Define specific browser support guidelines

[aweary]

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]

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:

• ReactDOMFiberInput controlled radio check
• ReactDOMInput controlled radio check
• ReactDOM Compat mode check
• CSSProperty.js
• CSS Property shorthand
• EnterLeave plugin ownerDocument
• ReactBrowserEventEmitter mountAt
• setTextContent
• SyntheticUIEvent view polyfill
• getEventCharCode
• getEventModifierState: Safari does not support getModifierState until 10.1

[nhunzaker]

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

[sophiebits]

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.

[aweary]

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

[sophiebits]

okay can't wait

[aweary]

@spicyj 🐛

[sophiebits]

Sorry, maybe next week. :(

[blling]

Any final plan?