When entering a BIP-39 seed phrase when restoring a wallet, some words that are prefixes of other words, when entered, cause the cursor to automatically jump to the next word field, even though the user may have wanted to enter one of the longer words. The user must thus tap backspace or tap the previous word field to continue entering the desired word.
For example:
"sad" is a prefix of "saddle" and "sadness".
"you" is a prefix of "young" and "youth".
"sea is a prefix of "search", "season", and "seat".
When attempting to enter "sadness", the cursor jumps to the next word field immediately "sad" is entered. Likewise for any of the other example long words when the corresponding short word is entered.
This does not happen with all such prefix words, e.g. when trying to enter "vanish", the cursor does not jump to the next word field once "van" is entered, even though "van" is in the wordlist.
Version
4.0.38 via F-Droid
Steps to reproduce
Set up a new wallet > On this device > Restore wallet
Try to enter any of the example long words in any of the word fields.
Expected behaviour
The cursor should not jump to the next word field unless (a) there is only one valid word that begins with the characters entered so far; or (b) the user taps one of the suggested complete words beneath the keyboard.
Actual behaviour
Observe that the cursor instead jumps to the next word field once a valid prefix word has been entered.
Description
When entering a BIP-39 seed phrase when restoring a wallet, some words that are prefixes of other words, when entered, cause the cursor to automatically jump to the next word field, even though the user may have wanted to enter one of the longer words. The user must thus tap backspace or tap the previous word field to continue entering the desired word.
For example:
When attempting to enter "sadness", the cursor jumps to the next word field immediately "sad" is entered. Likewise for any of the other example long words when the corresponding short word is entered.
This does not happen with all such prefix words, e.g. when trying to enter "vanish", the cursor does not jump to the next word field once "van" is entered, even though "van" is in the wordlist.
Version
4.0.38 via F-Droid
Steps to reproduce
Expected behaviour
The cursor should not jump to the next word field unless (a) there is only one valid word that begins with the characters entered so far; or (b) the user taps one of the suggested complete words beneath the keyboard.
Actual behaviour
Observe that the cursor instead jumps to the next word field once a valid prefix word has been entered.
Device or machine