New issue
Advanced search Search tips

Issue 912032 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 2
Type: Bug



Sign in to add a comment

Switch Back to Keyboard Autofill Manual Fallback

Project Member Reported by martijnb@chromium.org, Dec 5

Issue description

This is a scenario:
A form requires an Address Number and Address Street, but this is separated in two form fields. A user that is using the manual fallback can only fill the Address Number and Address Street combined. 

Because the form won't parse as a result, the user will have to focus the Address Street field and remove the Address Number from it. 

There are two possible clues that tell us that the user wants to go back to the keyboard. It's up to eng to see which state is easier to identify. 

Clue 1:
The user repositions the cursor into a field that has already been filled using manual fallback. 

Clue 2:
The user partially selects/ highlights characters of the string in a field that has already been filled using manual fallback. 


Based on which of the 2 clues is easier for eng to identify we will use one to switch to the keyboard. 
 
Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment