-
Notifications
You must be signed in to change notification settings - Fork 65
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
support matrix #56
Comments
For people on IE 9 or IE 10, would the removed functionality be easily provided by the same polyfills they'd use for React? |
Not really, apart from rAF, since most of the stuff here are essentially polyfills |
let's remove IE8 support and see what's left. bootstrap annoyingly supports ie10 so we wouldn't get big jump in features anyway |
Is it ready to release? |
Friendly ping @jquense |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
what browsers should we actually support here? RB has a bottom at ie11, and that seems fairly standard now, should we do that? react still theoretically supports ie9+ but in practice it asks you to pollyfill things like RAF, and really only handles the inconsistencies in places where it's not much more work above the ie11 support
In a quick run through i think we'd be able to remove a fair bit of cruft doing ie11+, removing ie8 gets us a lot but the ie9-10 support is not nothing. Question is who is stuck on ie9-10? In practice those people are almost certainly on ie11. I've never had a support issue for ie9-10 specifically
The text was updated successfully, but these errors were encountered: