21148 2013-02-27 21:24:53 +0000 Provide <input> element attribute to suppress input caching and/or prediction 2013-04-12 17:23:00 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified All All RESOLVED WORKSFORME P2 normal --- 1 addison dave.null devarshipant mike public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 83814 0 addison 2013-02-27 21:24:53 +0000 Use case: an application has a screen for entering new user information. A predictive keyboard cannot effectively predict people names, so input prediction should be off. In addition, filling the field from browser-cached form input data is not useful, as invariably the information needs to be replaced. Suggestion: add a new attribute for the <input> element as a hint to the user-agent that populating the field with cached form input data is not desired (and/or turn off auto-completion). Perhaps something like: <input type="text" name="fullname" private> Or perhaps: <input type="text" name="fullname" autocomplete="false"> 86026 1 robin 2013-04-12 10:02:27 +0000 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: Accepted Change Description: none Rationale: We have that with autocomplete=off. The "off" keyword indicates either that the control's input data is particularly sensitive (for example the activation code for a nuclear weapon); or that it is a value that will never be reused (for example a one-time-key for a bank login) and the user will therefore have to explicitly enter the data each time, instead of being able to rely on the UA to prefill the value for him; or that the document provides its own autocomplete mechanism and does not want the user agent to provide autocompletion values.