1020819 - [meta] Honour field attributes/restrictions in Form Autofill

Status: NEW

(Toolkit :: Form Autofill, defect)

Description

[Matthew N. [:MattN]]

A user may have a completed or incomplete auto-fill profile which doesn't meet the requirements of the <form> that requestAutocomplete was called on. We need to ensure that we don't perform any action that a user couldn't manually do or cause validity issues (except apparently @pattern is exempt for some reason).

"A user agent prefilling a form control's value must not cause that control to suffer from a type mismatch, suffer from being too long, suffer from being too short, suffer from an underflow, suffer from an overflow, or suffer from a step mismatch. Except when autofilling for requestAutocomplete(), a user agent prefilling a form control's value must not cause that control to suffer from a pattern mismatch either. Where possible given the control's constraints, user agents must use the format given as canonical in the aforementioned table. Where it's not possible for the canonical format to be used, user agents should use heuristics to attempt to convert values so that they can be used."

IMO the conversion heuristics should be handled in separate bugs from the initial bugs which prevent invalid data from being autofilled.

There is more information and examples at http://www.whatwg.org/specs/web-apps/current-work/#processing-model-2

Comment 1

[Matthew N. [:MattN]]

Once the UX of how to handle a mismatch between a profile and a form's requirement is settled in bug 1020829, dependencies for implementing the UX can be filed.

Comment 2

[Matthew N. [:MattN]]

This bug still applies to Form Autofill so I'm morphing it.