-
Notifications
You must be signed in to change notification settings - Fork 80
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
hybrid components throw invariant error in IE11 #220
Comments
waiting for repro steps |
Found one issue with the demo page but I don't think it's related to the core issue being talked about there. |
jondlm
added a commit
that referenced
this issue
May 5, 2016
There's a more general issue with how we're defining our components. Solution is to stick all of our non-standard properties on |
sodiumjoe
added a commit
to sodiumjoe/lucid
that referenced
this issue
May 7, 2016
…riant error Change createClass to explicitly pass through the component definition so buildHybrid can grab the explicit statics instead of inferring them from the top-level component definition properties. This lets us avoid accidentally colliding with any React default class properties, which causes an invariant error.
addressed in #224 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: