Block a user
Component / Participant picker
Text input component
In practical implementation, probably not, that was how the component was designed in the specification.
Text input component
I’d keep the error prop for now. Native validation works for some cases but gets awkward once you have server errors or custom validation. An explicit error state keeps the component predictable.
Text input component
For certain cases, yes, it probably should. I've added inherit as a default. However, we need to be able to override it like in the TextInput component. Here, the icon is in a dedicated container…