-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
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
TextField ignores prop InputProps{disableUnderline} and passes it down to DOM element. #15502
Comments
Can you follow and fill out the issue template please. A code example is ideal as well. I would make sure you are using |
Completed. You caught the issue faster than I completed the template, that's service! :) |
Is there anyway to remove the underline from a textfield without the browser error using material ui 4.9 ? |
Note that |
"@material-ui/core": "^4.9.14", The component in question is a filled Textfield. -> React does not recognise the disableUnderline prop on a DOM element. |
#15502 (comment) |
Both are accepted and does different things? Should i stop using inputProps all together? thanks |
See #11377 |
Even though standard is the default variant, I get this runtime error if I don't explicitly specify |
Hey everyone! I encountered similiar issue. I am disabling underline right in the theme. Everything works but I get the " React does not recognize the
|
Expected Behavior 🤔
Docs say should remove the underline from the nested Input Field.
Current Behavior 😯
Either TextField or Input is ignoring the prop. React Errors: "React does not recognize the
disableUnderline
prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercasedisableunderline
instead. If you accidentally passed it from a parent component, remove it from the DOM element."Similar to #13717 But looks like they only addressed TextField variant 'filled'.
Still exists @material-ui/core": "3.9.3"
Steps to Reproduce 🕹
Link:
Context 🔦
Just trying to render a TextField variant="outlined" without it underlining the input field, without hacking the css.
Your Environment 🌎
The text was updated successfully, but these errors were encountered: