This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13569 - Allow user agents to override autocomplete
Summary: Allow user agents to override autocomplete
Status: VERIFIED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://dev.w3.org/html5/spec/common-i...
Whiteboard:
Keywords: a11y, a11ytf
Depends on:
Blocks:
 
Reported: 2011-08-03 03:43 UTC by Cynthia Shelly
Modified: 2011-12-23 20:37 UTC (History)
7 users (show)

See Also:


Attachments

Description Cynthia Shelly 2011-08-03 03:43:38 UTC
"A user agent may allow the user to override the resulting autocompletion state and set it to always on, always allowing values to be remembered and prefilled), or always off, never remembering values. However, the ability to override the resulting autocompletion state to on should not be trivially accessible, as there are significant security implications for the user if all values are always remembered, regardless of the site's preferences."


Certain types of user agents may need to make these options more obvious, for example to users with cognitive disabilities who need to have their PC remember all of their passwords.  Is that a normative SHOULD?
Comment 1 Anne 2011-08-03 06:23:24 UTC
It's a normative should not and makes sense for the majority case. The user agents you mention have a good reason to go against it. I don't see what the problem is here.
Comment 2 Michael[tm] Smith 2011-08-04 05:00:21 UTC
mass-moved component to LC1
Comment 3 Ian 'Hixie' Hickson 2011-08-09 20:10:25 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: 

> Certain types of user agents may need to make these options more obvious, for
> example to users with cognitive disabilities who need to have their PC remember
> all of their passwords.

That's exactly why it's a SHOULD and not a MUST.