You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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: