-
Notifications
You must be signed in to change notification settings - Fork 75
Description
Our app currently ignores unconfirmed/underlined text on Android devices (see these reports for example: https://merginmaps.slack.com/archives/C02DWECUEN8/p1769847621711129, #4285) until it is confirmed.
Some languages rely on the unconfirmed text to enter proper characters (Japanese, Korean, Indian,...). The underline indicates a "Composing" state (e.g., typing "Tokyo" phonetically to get "東京").
This is an example of how the underline text looks like:

The app currently waits until the text is confirmed (by hitting space, dot, enter, back button, choosing a suggestion and more) to perform an action (validate input, search, ...). This results in a weird and unnatural UX when the app does not react to the input. People expect to see the app make an action immediately.
Let's do the following:
- Make the app react to the unconfirmed text immediately (hint: explore
TextInput'spreeditTextanddisplayTextprops). This applies to:- Various text inputs across the app -> search bars (project, features, layers search )
- Text and number inputs within the feature form
- Text inputs in other parts (sign in/up forms, close account, ...)
- In general, we need to implement the fix in the base input components and it should propagate to the entire app automagically
Acceptance criteria:
- The app does not wait for text confirmation (space, enter, suggestion selection) to perform the desired action.
- The fix works on Android and iOS, for multiple popular keyboards (at least Samsung, Apple, Google and Microsoft SwiftKey keyboard)
- Number inputs responds immediately too (verify numbers, minus sign, decimal separator sign)
Important
Note for testers: Please verify also scenarios in tickets marked as duplicates of this ticket.