react-draft-wysiwyg
react-draft-wysiwyg copied to clipboard
Warning: Can't call setState
When I click on the editor I get this warning in the console:
Warning: Can't call setState on a component that is not yet mounted. This is a no-op, but it might indicate a bug in your application. Instead, assign to this.state directly or define a state = {}; class property with the desired state in the r component.
I made a codeSandbox where it is too: https://codesandbox.io/s/brave-architecture-4zpm5
Its only in StrictMode I get the warning: https://codesandbox.io/s/strange-monad-lxtuu?file=/src/index.js
@sirvival3 did you find the solution of this issue. I am getting same problem?
Is there any solution to this? I am getting the same error.
Me too
Same error
Any news about this warning?
This issue still persists, and there is a PR pending to be merged which i believe fixed the issue, can the owner kindly review and merge the PR
@jpuri is there any chance we can have PR merged which fixes the issue?
Any news?
Is this thing abandoned?
Literally checked so many boards all the same desperate cries for help. #mergethedangfix
I would like to understand why does this warning not appear in some demos? E.g., the demo at https://jpuri.github.io/react-draft-wysiwyg/#/ does not give the warning.
any fix?
For me its not the error itself. It's knowing that there is a solution ready but apparently noone paying attention to mantaining this package. I'll just use CKE.
hmmm still have this issue, I use Next.js and I try to disable reactStrictMod, but no result... :s
Guys any fix yet? -_-
I got the same error
also got the same error
@jpuri Any word on if the possible fix https://github.com/jpuri/react-draft-wysiwyg/pull/1044 could be merged? Thanks in advance.
@jpuri any fixes yet??
Still same error.
Still no fixes I see :|
We replaced it with React Quill instead because of this issue.
Still same error.
Still same error!
The same... 😢😢😢
Doesn't anyone care about this package i'm getting the same error
i'm also facing the same problem
Somehow worked by Just removing "StrictMode" from my app.
Ok, so is this project dead or what? Ignoring this bug for 2 years is insane. "just remove strict mode" is not a solution. Definitely not a prod-ready lib anymore.