-
-
Notifications
You must be signed in to change notification settings - Fork 49.8k
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
Using <Button> results in "findDOMNode is deprecated in StrictMode" warning #22493
Comments
retiring the <React.StrictMode> tag in method ReactDOM.render() works normally |
I am getting same error in strict mode antd v4.0.4
|
Is there any solution regarding the same or any suggestions would also be appreciated. |
Removing strict mode just for the sake of a button is ridiculous. This is a legit problem with antd that needs to be fixed. |
I am getting the same error |
Need to do a lot of migration, such as #9870 |
The same here after a fresh install using the guide https://ant.design/docs/react/use-in-typescript |
I have the same problemdescWarning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of Wave which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here: https://fb.me/react-strict-mode-find-node solveReactDOM.render(
// <React.StrictMode>
<App />
// </React.StrictMode>,
,
document.getElementById('root')
); |
I have the same issue. Can you fix it, please? |
1 similar comment
I have the same issue. Can you fix it, please? |
I have the same issue, but I'm using other components, so the problem is not just the |
I have the same problem. I'm using <InputMask ...> which comes from the "react-input-mask" library. I also use "material-ui" for the TextField element.
The line in question seems to be the <TextField {...inputProps} /> line. |
disabling strict mode is not really an option. How can we fix this? |
Contribute to migration code about this. |
I'm having this problem in SubMenu and Select components too. |
I got the same warning |
Same issue |
Same issue also :( |
One more here, working with disabled <React.StrictMode>, but really hope it's not a longterm solution. |
Same issue |
Same issue here. |
Same problem here, does Ant team already have a solution? |
Menu also produces this warning: I guess it could be a big thing to refactor this. It may be needed to dig into multiple components.
|
Same issue, help!!! please. |
Same issue with BackTop button |
Menu.Item it's also causing these logs. |
Any update about this? |
Same issue with Slider. |
same issue with antd@4.13.0 for Submenu |
same issue with antd@4.12.3 for DomWrapper |
same issue in antd@4.13.1 for submenu |
samee issue is has it been solved ? |
same issue in antd@4.14.0 for slider |
same issue with Image antd@4.14.1" |
same issue with |
Same issue with |
Same issue antd 4.15.0 |
Same issue with |
Same issue with |
Do not close this issue. 掩耳盗铃 is stupid! |
Been waiting for a fix for 6months. Hopefully, it can be fixed soon! |
same issue here on clicking |
I'm getting this too on slider. This needs to be fixed! I don't know why this issue was ever closed. The proposed solution is not very nice at all. Whoever is working on this repo please fix it - I feel like this should be an easy fix. |
???????????????????????? CLOSED????????? |
|
???????????????????????? CLOSED????????? |
Same issue here! This hasn't fixed yet? |
???????????????????????? CLOSED????????? |
Same issue for Affix, and MenuItems. |
Closed?????????????????? The problem still here and hasn't fixed?????????????????? |
trace in #26136 |
Reproduction link
latobibor/antd-tryout@e373cb5
Steps to reproduce
What is expected?
No warnings should be displayed.
What is actually happening?
A warning message will appear in console.log stating "Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of Wave which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here:"
The source of the problem is coming from
<Button />
component.See the file in question:
latobibor/antd-tryout@e373cb5#diff-b525f6f7c3584f9af17112d37dae3a42
The text was updated successfully, but these errors were encountered: