Material-ui: TextField disabled value

Created on 10 Oct 2017  路  4Comments  路  Source: mui-org/material-ui

When a TextField has disabled={true}, I have to use value={someState} instead of the defaultValue={someState}. For the opposite scenario (disabled={false}) I have to use defaultValue={someState} to make my TextField editable.

Is this intentional?
Thanks for the great work guys :-)

bug 馃悰 v0.x

Most helpful comment

@tathagatbanerjee We have the to begin of a migration guide

All 4 comments

Not sure if related, but I am seeing behaviour where onTouchTap works past 0.18.7 even if disabled is set to true. Obviously, I need to change my code to use onClick, but a disabled button will trigger irrespective of disabled if you have used onTouchTap as opposed to onClick.

We have been porting the component on the v1-beta branch. We reimplemented it from the ground-up. While we haven't tested it, I think that the issue is most likely fixed on that branch. Hence, I'm closing it.
Still, we will accept PR fixes until v1-beta takes over the master branch.

Hey mate - all good. really looking forward to the new one. it looks epic btw. I wish my js skills were up to helping out. Is there a recommened way to upgrade? Like install both simultaneously and slowly upgrade, or is it expected to a big bang style? thanks so much.

@tathagatbanerjee We have the to begin of a migration guide

Was this page helpful?
0 / 5 - 0 ratings

Related issues

chris-hinds picture chris-hinds  路  3Comments

pola88 picture pola88  路  3Comments

ryanflorence picture ryanflorence  路  3Comments

mattmiddlesworth picture mattmiddlesworth  路  3Comments

sys13 picture sys13  路  3Comments