-
Notifications
You must be signed in to change notification settings - Fork 47.5k
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
#2327 : Use this._rootNodeID in componentDidMount of ReactDOMInput #2345
#2327 : Use this._rootNodeID in componentDidMount of ReactDOMInput #2345
Conversation
If we do this, we should do it for
@zpao @sebmarkbage I added |
Yes, I thought that while reading the code but I wanted to restricted myself as close as the issue which was about componentDidMount. And I didn't know if there were reasons to get the DOM node in componentWillUnmount. |
@ThomasCrvsr Yeah I'd say so, getting the same ID from two different places is just asking for trouble :) |
It's used in |
Can I call directly otherNode._rootNodeID in _handleChange ? I have weird behavior in test when I try to use this. |
Hmm, no you can't because it's a DOM node. I guess Argh, the correct solution is probably to leave it as it was, but only set/use |
It's already the case isn't it ? |
@ThomasCrvsr for |
After some more thought... The radio workaround is pretty much a big hack, are we OK with simply assuming that Devs, what's your take? |
I was planning on refactoring the internals so that they're not exposed on composite component classes. This would not work in the future anyway. Will close out for now. This perf improvement is noted though. |
No description provided.