According to material 3 OutlinedTextField specs, we need to show the error message in supporting text. (source: https://m3.material.io/components/text-fields/specs#cf537769-a896-47b0-b56b-8da09e0e00c2)

- When there is a supporting text, and an error occurs, should we show the error instead of the original supporting text? It means that we'll need to have a logic for which text to show.

- When talkback is enabled, and there is a supporting text, tapping on the field reads that supporting text along with other announcements. When there is an error, textfield defaults error semantics to "Invalid input", and in order to update it we need to change error semantics and pass the actual error. Also we update the supporting text to show the actual error. Now tapping on the text field announces both supporting text and error, which results in actual error announced twice. This can be mitigated by clearing the semantics of the supporting text. But we'll need to do that on the error state, because we want supporting text to be announced if it is a normal text.

These complicate error state handling within a text field. There should be a slot for errors and these kinds of logic should happen internally.

Jetpack Compose version:
Compose bom: 2024.12.01

Jetpack Compose component(s) used:
TextField with supporting text, semantics modifier

Android Studio Build:
Android Studio Ladybug | 2024.2.1 Patch 3

Kotlin version:
2.0.0

Issue 397934762

Links (2)

Issue metadata