We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Do you want to request a feature or report a bug?
Bug.
What is the current behavior?
SyntheticEvent.js breaks in IE11.
SyntheticEvent.js
Object.assign is explicitly used to extend the prototype of SyntheticEvent.
Object.assign
SyntheticEvent
react-tap-event-plugin/src/SyntheticEvent.js
Line 123 in f7ed5c5
What is the expected behavior?
SyntheticEvent.js should work.
Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
Broken in React 16 + IE11 + react-tap-event-plugin. It used to work in React 15 + IE11 + react-tap-event-plugin.
react-tap-event-plugin
Is the recommended approach to use babel to polyfill Object.assign?
See facebook#11788
The text was updated successfully, but these errors were encountered:
I am having the same issue when running on Android 5.1. Please consider avoiding Object.assign or build the dist bundle with babel.
Sorry, something went wrong.
No branches or pull requests
Do you want to request a feature or report a bug?
Bug.
What is the current behavior?
SyntheticEvent.js
breaks in IE11.Object.assign
is explicitly used to extend the prototype ofSyntheticEvent
.react-tap-event-plugin/src/SyntheticEvent.js
Line 123 in f7ed5c5
What is the expected behavior?
SyntheticEvent.js
should work.Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
Broken in React 16 + IE11 +
react-tap-event-plugin
. It used to work in React 15 + IE11 +react-tap-event-plugin
.Is the recommended approach to use babel to polyfill
Object.assign
?See facebook#11788
The text was updated successfully, but these errors were encountered: