Skip to content
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

Error on opening property editor #347

Open
Nickhoyer opened this issue Apr 9, 2021 · 9 comments
Open

Error on opening property editor #347

Nickhoyer opened this issue Apr 9, 2021 · 9 comments

Comments

@Nickhoyer
Copy link

Warning: React does not recognize the inputRef prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase inputref instead. If you accidentally passed it from a parent component, remove it from the DOM element.

Getting this in console in my React 17 project

@redDSsun
Copy link

redDSsun commented May 6, 2021

i got the the same warning

@miketwo
Copy link

miketwo commented May 19, 2021

fwiw, this was what it looked like for me. I'm using MaterialUI as well. I wonder if it's a React DevTools problem...?

image

@Zvi7Ping
Copy link

Zvi7Ping commented May 23, 2021

I am having the same warning and am not using MaterialUI. It appear every time the variable-editor modal appear. Does anyone have ideas/suggestions?

@alexchanwk
Copy link

It was caused by the VariableEditor passing prop "inputRef" to AutosizeTextarea.
AutosizeTextarea had changed to use prop "ref" instead of "inputRef", and the prop "inputRef" was not handled and passed to the textarea element, which React does not recognize and gave that warning.

@Mustafa-Agha
Copy link

@alexchanwk is there a solution for this bug

@tjnk24
Copy link

tjnk24 commented Nov 11, 2021

got same problem with react-json-view: 1.21.3, react: 17.0.1, antd: 4.16.13,

@sp0033212000
Copy link

I have the same problem. Is there a solution?

@enricomad
Copy link

enricomad commented Dec 7, 2021

@sp0033212000 @tjnk24 #374 solves the issue, but i did not get any updates on it since i opened it.

@dranitski
Copy link

upvote the fix by @enricomad #374 🆙

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants