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
Additionally, we may leave the syntax level IE 9 (var everything), and then provide an additional polyfill for users who still want IE9 support (including Map, Set, requestAnimationFrame, and cancelAnimationFrame).
Very welcome. However I suggest to not to create ie9 polyfill. By letting the very small amount of people using obsolete browsers, giving them life jackets to continue doing so will lessen the chances of them upgrading to a more secure version of their current browser.
Reacted by Vadim Yakhin, gutbk201 and Rafael T
Reacted by Matthäus J. N. Beyrle, s-ve and Adam Hoddinott
We ended up not doing anything—people opted into dropping those browsers by updating to React 16. Those who didn't want to could add polyfills themselves.
Activity
Timer commentedon Sep 28, 2017
Additionally, we may leave the syntax level IE 9 (
vareverything), and then provide an additional polyfill for users who still want IE9 support (includingMap,Set,requestAnimationFrame, andcancelAnimationFrame).oriSomething commentedon Sep 28, 2017
@Timer Maybe splitting to 2 builds by using
nomodulefeature for the newer browsers?andriijas commentedon Oct 2, 2017
Very welcome. However I suggest to not to create ie9 polyfill. By letting the very small amount of people using obsolete browsers, giving them life jackets to continue doing so will lessen the chances of them upgrading to a more secure version of their current browser.
gaearon commentedon Jan 8, 2018
We ended up not doing anything—people opted into dropping those browsers by updating to React 16. Those who didn't want to could add polyfills themselves.