Make sure a text input view displays the correct AutoFill suggestions.
To ensure your text input view displays the right AutoFill suggestions, set the
text property on any relevant input views.
Use the following
Explicitly defining a view’s text content type improves the performance of Password AutoFill’s heuristics and lets you support login workflows that couldn’t otherwise be detected by these heuristics. For example, the heuristics assume the user name and password inputs are on the same page. If you have a multipage login form, explicitly setting the
.password types lets the user tap and fill those inputs, even if they are on separate pages.
By default, the system selects the a keyboard based on the input view’s
text property; however, you can mix the input view’s text content type and keyboard type to explicitly define the desired keyboard. For example, if your site uses email addresses as user names, set the input view’s
text property to
username, and set the
keyboard property to
This example defines text fields for logging in:
When creating a new account or changing the password, use the
new text content type instead:
Additionally, you can autocomplete security codes from single-factor SMS login flows:
For more information on how to enable Password AutoFill behavior in web apps, see Enabling Password AutoFill on an HTML Input Element.