-
Notifications
You mu 8000 st be signed in to change notification settings - Fork 48.5k
Invariant Violation: ReactMount: Two valid but unequal nodes with the same data-reactid
#1436
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
Comments
Could this be related? #1400 Also, we're all on the advertised IRC-channel if you want more direct communication. |
@syranide Yes message is the same, but cause looks for me different. When first image unmounted later when 'load' happen it uses previous dom representation with old reactid, which is already used by another node. |
While it's hard to tell, it could be that you've run into this bug: #1147 I don't remember the exact cause of the bug, but it's something like if you have Root -> Child, if you issue an update to Root and Root directly issues an update on Child (setProps, setState or forceUpdate). Child then updates, but afterrwards the initial update to Root will propagate as usual causing Child to update again, which causes the DOM to be incorrectly overwritten. Sounds like it could be related or totally not? :) |
Nope, #1147 rather complex but not my case. |
Right, if you stop by IRC I could take a look at the link if it's ok, I don't think there's any way to send private information via github? |
Want to submit a PR? Will close this in favor of #1400. |
have a same data-id.you mouse mine another plugin tools copy same dom. example swiper loop param.it will copy same dom in you DOC. 坑 |
The same happen with 0.10 and master.
I am sorry i could not make reproducible test case.
That is stack trace for master:
And for 0.10
Generaly happen such things:
Main component render first time
img
, then componentDidMount get data via ajax, and on response it update state, then in renderimg
replaced with another component. In moment later it call react trap for 'load' event on previousimg
and exception happen.I appreciate feedback and help with issue. I have public link for debuging, but i could not share it with public, so if someone want to see it in action let me know pls.
The text was updated successfully, but these errors were encountered: