New onboarding: Seed Phrase Entry UX Issues

[glitchminer]

Metadata

• Original Issue Numbers: 18, 19, 20
• Source: New onboarding integration (happy paths) #17045 (comment)

Issue 18 - Incorrect focus after paste

Field	Description
Current Behavior	After pasting, focus remains on the 11th, 16th or 21st field instead of the final one
Expected Behavior
Location/Screen	Seed phrase entry
Figma URL

Issue 19 - Auto-focus behavior differs from design

Field	Description
Current Behavior	On completion of a valid word the focus is moved to the next field automatically
Expected Behavior	Pressing enter moves to next field when valid
Location/Screen	Seed phrase entry
Figma URL	https://www.figma.com/design/Lw4nPYQcZOPOwTgETiiIYo/Desktop-Onboarding-Redesign?node-id=403-50297&m=dev

Issue 20 - Backspace behavior incorrect

Field	Description
Current Behavior	Double clicking a word so it is highlighted and pressing backspace deleted one character and opened the type-ahead suggestion menu instead of clearing the field
Expected Behavior	Fields can be cleared by selecting a word and pressing backspace or delete
Location/Screen	Seed phrase entry
Figma URL	https://www.figma.com/design/Lw4nPYQcZOPOwTgETiiIYo/Desktop-Onboarding-Redesign?node-id=403-52841&m=dev

[caybro]

Ad Issue 19; I believe the behavior is correct (pressing Enter being equivalent to selecting the item with mouse), cf:

[glitchminer]

@caybro , for 19, the example you gave is fine but the issue is about the behaviour when return is pressed while the typeahead menu is not open.

[caybro]

@caybro , for 19, the example you gave is fine but the issue is about the behaviour when return is pressed while the typeahead menu is not open.

OK, this is definitely existing (and looks like intended) behavior; can you confirm @benjthayer ?

[caybro]

The other 2 issues are reproducible bugs, fixing.

[benjthayer]

@caybro , for 19, the example you gave is fine but the issue is about the behaviour when return is pressed while the typeahead menu is not open.

OK, this is definitely existing (and looks like intended) behavior; can you confirm @benjthayer ?

Sorry @caybro @glitchminer could you clarify the behaviour that is suggested to be incorrect so I can check?

I see when I go to add a new address using a recovery phrase, the recovery phrase form blocks the user from pressing enter if there is no valid word displayed via the typeahead menu. I think this is fine if we want to retain this behaviour - it stops the user from entering a wrongly spelled word accidentally and then having to go back through the form to fix the issues. Not sure if that was the question?

Of course the user should be able to enter an invalid word and click into another field which would then show the validation that the word previously entered is not valid.

[glitchminer]

Hi @caybro @benjthayer , I think the question is about what this part means: "Pressing "Enter" validates the field. If entered word is valid, the next input is focused".

I understood it to mean that if you click into a field that already contains a valid word and press enter (without making any further edits) then the focus should move to the next field. The typeahead menu does not open in that case.

The user can still use the tab key to move forward but this would happen without the validation mentioned.