You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
findDOMNode has been deprecated for several major versions (since 16, I think?). The docs have always said:
There is currently no direct equivalent for this use case, which is why findDOMNode is deprecated but is not yet removed completely from React
Leading me to believe that there would be an alternative mechanism for ref-ing a text node before this was removed. Unfortunately, this doesn't seem to be the case. I've opened an issue with the React folks, and we'll see if that goes anywhere. In the meantime, it's impossible to use React ProseMirror with React 19.
If React doesn't end up addressing this, then we are going to have to find an alternative approach to ref-ing our text nodes. I think we may be able to extend the code that we use to resolve text nodes in CompositionViewDescs to search for text nodes generally, but I'm worried about have to rely on assumptions about child nodes that might not be sufficiently robust.
The text was updated successfully, but these errors were encountered:
See also the issue on the React repo: facebook/react#31836
findDOMNode
has been deprecated for several major versions (since 16, I think?). The docs have always said:Leading me to believe that there would be an alternative mechanism for ref-ing a text node before this was removed. Unfortunately, this doesn't seem to be the case. I've opened an issue with the React folks, and we'll see if that goes anywhere. In the meantime, it's impossible to use React ProseMirror with React 19.
If React doesn't end up addressing this, then we are going to have to find an alternative approach to ref-ing our text nodes. I think we may be able to extend the code that we use to resolve text nodes in CompositionViewDescs to search for text nodes generally, but I'm worried about have to rely on assumptions about child nodes that might not be sufficiently robust.
The text was updated successfully, but these errors were encountered: