feat(@clayui/css): LPD-53483 Adds inline-text-input
https://liferay.atlassian.net/browse/LPD-53483
Shouldn't we be adding this to our docs site too? https://clayui.com/docs/components/input
@ethib137 Good catch, I'll update it.
Standard inputs are a fixed width and can't grow with its content. There is some discussion at https://liferay.atlassian.net/browse/LPD-53482?focusedCommentId=2911231
@ethib137 I've been trying to get the value to display in the contenteditable element, but I'm running into some React quirks. Using {value} in the contenteditable span causes the text cursor to move to the front which makes the text print out right to left.
I got it to work in uncontrolled mode by using
defaultValue. The controlled component doesn't work. I have a question about why we need to support both types. Is it really necessary?
What was the reason for using content editable instead of an unstyled input?
I was hoping Lexicon could revisit the design / interactions and accommodate the limitations of the standard HTML input.
Closing this since it was discarded, will reopen if revisited.