-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
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
DropdownMenu causing Uncaught Invariant Violation: findComponentRoot #3624
Comments
Thanks for raising this issue but that's a duplicate of #3586. |
I'm still seeing this issue, seems the PR in thew other issue was for Popover not DropDownMenu? |
@gazzer82 The |
I am using the latest version from NPM, should I try pulling directly from github? Sent from my iPhone On Mar 13, 2016, at 01:18, Olivier Tassinari <notifications@gitpro.ttaallkk.topmailto:notifications@github.com> wrote: @gazzer82https://github.com/gazzer82 The Popover is used internally by the DropDownMenu. Are you using the master branch? Reply to this email directly or view it on GitHubhttps://github.com//issues/3624#issuecomment-195919797. |
@gazzer82 You might try deleting your node_modules/material-ui folder and then npm install. That worked fine for me. |
@stueynet i have just tried that, no dice. |
Ok, so i manually changed the 'noscript' to 'div' in the compiles js popper.js button and that's fixed it for now. So i guess that PR hasn't made it into the NPM version, so i assume it will roll up in alpha.2 I did try pulling this from github and using that version, but i couldn't get Babel to play nice and convert the src files. Thanks Gareth |
Problem Description
Dropdown component causing dom change error in hot reload. When the basic Dropdown is rendered we get the following hot reloading error:
This is usually a result of bad formed HTML. We checked all components and only the Dropdown is causing this problem.
Versions
The text was updated successfully, but these errors were encountered: