sap.m.TextArea does not show valueState (chrome)

[sap]

sap.m.TextArea does not show valueState (chrome)

[aborjinik]

TextArea does not have valueStateText property.
I am not sure I get the input issue right

[hschaefer123]

;-) You are right. It has a valueState but not a valueStateText (very consequent).

From my Point-of-view that feature should be part of InputBase, because every input can lead to parse/validation errors and i need a unique/generic way to show field errors.

What do you mean?

So currently for TextArea this is a feature request, but the layout issue depends on Input fields placed inside dialogs. In most situations, the valueState will be shown under the input, but im some situation it will not get hided correctly. Maybe additionally a z-index issue besides the hide issue.

[aborjinik]

Initially InputBase was not designed only for writable fields. So the idea was using it for all type of html inputs like checkbox, radio, file... That's why InputBase does not have maxLength or it does not fire liveChange event. We could create a new control e.g TextField between InputBase and writable inputs and inherit Input,TextArea from TextField but now when we look at the framework it is only used for writable fields except DateTimeInput.

So from my point of view this is a valid feature request for InputBase any more.

I still could not reproduce the input issue but will look into it closer.

Thanks for your feedback.

[hschaefer123]

on chrome if i slowy click twice into the inputfield, it seems that the valueState will be brought to back without hiding (like screenshot). first click show error value state, second click pushes it back. Maybe this helps to reproduce (tested in jsbin)

[aborjinik]

OK I see the issue now. I will report to the control owner.
Thanks for your feedback.

[balexan]

Fixed in 1.24.

[akudev]

Also fixed in 1.22 now and fix will be in the next 1.20 patch (1.20.11). Closing. Thanks!