Ignite UI for Web Components is a complete library of UI components, giving you the ability to build modern web applications using encapsulation and the concept of reusable components in a dependency-free approach.
In the WebC repo in the Demos, I think that the Text Area behavior might be improved, and the current one might be a bug or not defined, I'm not sure.
Currently, if I write down something in the Text Area to have a Filled state of the Text Area when I switch to some other state (readOnly, spellcheck, validateOnly, required, disabled, or invalid), the filled text disappears. If there is a defined Placeholder, switching throughout the states is fine, and the Placeholder is still visible.
Description
In the WebC repo in the Demos, I think that the Text Area behavior might be improved, and the current one might be a bug or not defined, I'm not sure.
Currently, if I write down something in the Text Area to have a Filled state of the Text Area when I switch to some other state (readOnly, spellcheck, validateOnly, required, disabled, or invalid), the filled text disappears. If there is a defined Placeholder, switching throughout the states is fine, and the Placeholder is still visible.
Steps to reproduce
Result
https://github.com/IgniteUI/igniteui-webcomponents/assets/127843837/1996f86d-de4a-4b7b-8833-4ac8c384df2f
Expected result
To see the filled-in text after switching to another state.
Attachments