Confirmed users
183
edits
User:P.A./Form user experience improvements: Difference between revisions
Jump to navigation
Jump to search
User:P.A./Form user experience improvements (view source)
Revision as of 14:19, 28 May 2014
, 28 May 2014Add comparison of strategies
(Add approaches) |
(Add comparison of strategies) |
||
| Line 92: | Line 92: | ||
The website may display '''visible fields later in the process''' to correct any data validation errors. | The website may display '''visible fields later in the process''' to correct any data validation errors. | ||
== Comparison of strategies == | |||
One of the most difficult problems that '''form autofill''' has to deal with, for existing websites, is identifying which type of data is being requested by each form field. Authors can update the website to use the <code>autocomplete</code> attribute to help the browser, but the feature may not be available if the website doesn't do this. This can make it unclear to the user why one website supports autofill and another similarly-looking site doesn't. | |||
On the other hand, '''requestAutocomplete''' only works with websites that have changed their input flow to explicitly request some personal information from the browser. This feature shows a browser-provided interface that provides data to the website. While the feature could be used in an "unclear" way to populate visible fields, similarly to form autofill, we can ensure that the difference is clear by '''requiring that target form fields are hidden''' at the time of the request to autocomplete them. | |||