-
Notifications
You must be signed in to change notification settings - Fork 602
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
Add ref-forwarding to all Base and MSFT components #1668
Comments
+1 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
We could implement the |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I believe this is slated for our next major version, not stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
closed by #3517 |
It looks like React is deprecating
ReactDOM.findDOMNode
: https://reactjs.org/docs/react-dom.html#finddomnodeOur current reccomended to retrieve a DOM node is through that method, so I think we need to integrate ref forwarding into all of our components. While this should be pretty transparent for many components, there are several components that provide public properties on class instances, which we will need to provide alternate solutions for.
The text was updated successfully, but these errors were encountered: