RequestAutocomplete - Revision history

Hixie at 21:56, 9 April 2014

2014-04-09T21:56:24Z

← Older revision		Revision as of 21:56, 9 April 2014
Line 1:		Line 1:
			Something based on this is now in the HTML standard: http://www.whatwg.org/specs/web-apps/current-work/#dom-form-requestautocomplete

			The remainder of this page is for the historical record:

	requestAutocomplete proposed spec (as implemented in Chromium)		requestAutocomplete proposed spec (as implemented in Chromium)

Dbeam at 01:30, 4 April 2014

2014-04-04T01:30:37Z

← Older revision		Revision as of 01:30, 4 April 2014
Line 59:		Line 59:
	# Set the requestAutocompleteIsActive flag to false.		# Set the requestAutocompleteIsActive flag to false.

	When the user agent is said to asynchronously fail with a reason it ~~queue~~ an event to fire on the form element currently being operated on of a new AutocompleteErrorEvent with the type "autocompleteerror" and the reason specified.		When the user agent is said to asynchronously fail with a reason, it queues an event to fire on the form element currently being operated on of a new AutocompleteErrorEvent with the type "autocompleteerror" and the reason specified.

	[[Category:Proposals]]		[[Category:Proposals]]

Esprehn at 01:29, 4 April 2014

2014-04-04T01:29:43Z

← Older revision		Revision as of 01:29, 4 April 2014
Line 56:		Line 56:
	# Statically validate the constraints and:		# Statically validate the constraints and:
	#: a. If the result is negative asynchronously fail with the reason "invalid".		#: a. If the result is negative asynchronously fail with the reason "invalid".
	#: b. If the result is positive fire a simple event named "autocomplete" on the form element.		#: b. If the result is positive fire a simple event named "autocomplete" that bubbles on the form element.
	# Set the requestAutocompleteIsActive flag to false.		# Set the requestAutocompleteIsActive flag to false.

Dbeam at 01:29, 4 April 2014

2014-04-04T01:29:22Z

← Older revision		Revision as of 01:29, 4 April 2014
Line 35:		Line 35:

	# If we are not allowed to show a popup then asynchronously fail with the reason "disabled" and abort these steps.		# If we are not allowed to show a popup then asynchronously fail with the reason "disabled" and abort these steps.
	# If the ''requestAutocompleteIsActive'' flag is true or the form ~~element’s~~ autocomplete attribute evaluates to “off” then asynchronously fail with the reason "disabled" and abort these steps.		# If the ''requestAutocompleteIsActive'' flag is true or the form element's autocomplete attribute evaluates to “off” then asynchronously fail with the reason "disabled" and abort these steps.
	# Optionally asynchronously fail with the reason "disabled" and abort these steps.		# Optionally asynchronously fail with the reason "disabled" and abort these steps.
	#: (For example the user agent may give the user an option to ignore all autocomplete requests.)		#: (For example the user agent may give the user an option to ignore all autocomplete requests.)
Line 51:		Line 51:
	# Optionally asynchronously fail with the reason "cancel" and abort these steps. (For example if the user cancels the request.)		# Optionally asynchronously fail with the reason "cancel" and abort these steps. (For example if the user cancels the request.)
	# For each tuple in the autofill set:		# For each tuple in the autofill set:
	#: a. Skip this tuple if the ~~input’s~~ attribute value for autocomplete is different than the one stored in the tuple.		#: a. Skip this tuple if the input's attribute value for autocomplete is different than the one stored in the tuple.
	#: b. Skip this tuple if the form owner of the input is not this form element.		#: b. Skip this tuple if the form owner of the input is not this form element.
	#: c. Autofill the input following the autocomplete rules but allowing the input to suffer from a pattern mismatch.		#: c. Autofill the input following the autocomplete rules but allowing the input to suffer from a pattern mismatch.

Dbeam at 01:29, 4 April 2014

2014-04-04T01:29:01Z

Dbeam at 01:28, 4 April 2014

2014-04-04T01:28:26Z

← Older revision		Revision as of 01:28, 4 April 2014
Line 55:		Line 55:
	#: c. Autofill the input following the autocomplete rules but allowing the input to suffer from a pattern mismatch.		#: c. Autofill the input following the autocomplete rules but allowing the input to suffer from a pattern mismatch.
	# Statically validate the constraints and:		# Statically validate the constraints and:
	#: a. If the result is negative asynchronously fail with the reason ~~“invalid”~~.		#: a. If the result is negative asynchronously fail with the reason "invalid".
	#: b. If the result is positive fire a simple event named ~~“autocomplete”~~ on the form element.		#: b. If the result is positive fire a simple event named "autocomplete" on the form element.
	# Set the requestAutocompleteIsActive flag to false.		# Set the requestAutocompleteIsActive flag to false.

Dbeam at 21:59, 2 April 2014

2014-04-02T21:59:02Z

← Older revision		Revision as of 21:59, 2 April 2014
Line 5:		Line 5:
	== Issues ==		== Issues ==

	This should really use a promise: http://dom.spec.whatwg.org/#promises		This should really use a promise: http://dom.spec.whatwg.org/#promises (http://crbug.com/343630).

	== Interfaces Additions==		== Interfaces Additions==

Annevk: this should use a promise

2013-06-06T09:21:36Z

this should use a promise

← Older revision		Revision as of 09:21, 6 June 2013
Line 2:		Line 2:

	This document contains a preliminary specification of the requestAutocomplete feature that allows developers to request that the browser fill a form with information based on the autocomplete attributes on the form controls.		This document contains a preliminary specification of the requestAutocomplete feature that allows developers to request that the browser fill a form with information based on the autocomplete attributes on the form controls.

			== Issues ==

			This should really use a promise: http://dom.spec.whatwg.org/#promises

	== Interfaces Additions==		== Interfaces Additions==

Annevk at 19:14, 23 March 2013

2013-03-23T19:14:00Z

← Older revision		Revision as of 19:14, 23 March 2013
Line 11:		Line 11:

	enum AutoCompleteErrorReason {		enum AutoCompleteErrorReason {
			"",
	"cancel",		"cancel",
	"disabled",		"disabled",

Dbeam: /* Interfaces Additions */

2013-03-23T00:09:58Z

Interfaces Additions

← Older revision		Revision as of 00:09, 23 March 2013
Line 22:		Line 22:

	dictionary '''AutocompleteErrorEventInit''' : EventInit {		dictionary '''AutocompleteErrorEventInit''' : EventInit {
	AutoCompleteErrorReason reason = “”;		AutoCompleteErrorReason reason = "";
	};		};

← Older revision		Revision as of 01:29, 4 April 2014
Line 34:		Line 34:
	When the '''requestAutocomplete'''() method is invoked, the user agent must run the following steps:		When the '''requestAutocomplete'''() method is invoked, the user agent must run the following steps:

	# If we are not allowed to show a popup then asynchronously fail with the reason ~~“disabled”~~ and abort these steps.		# If we are not allowed to show a popup then asynchronously fail with the reason "disabled" and abort these steps.
	# If the ''requestAutocompleteIsActive'' flag is true or the form element’s autocomplete attribute evaluates to “off” then asynchronously fail with the reason ~~“disabled”~~ and abort these steps.		# If the ''requestAutocompleteIsActive'' flag is true or the form element’s autocomplete attribute evaluates to “off” then asynchronously fail with the reason "disabled" and abort these steps.
	# Optionally asynchronously fail with the reason ~~“disabled”~~ and abort these steps.		# Optionally asynchronously fail with the reason "disabled" and abort these steps.
	#: (For example the user agent may give the user an option to ignore all autocomplete requests.)		#: (For example the user agent may give the user an option to ignore all autocomplete requests.)
	# Set the ''requestAutocompleteIsActive'' flag to true.		# Set the ''requestAutocompleteIsActive'' flag to true.
Line 49:		Line 49:

	# Let the autofill set be the set of autocomplete tuples that were passed into this algorithm.		# Let the autofill set be the set of autocomplete tuples that were passed into this algorithm.
	# Optionally asynchronously fail with the reason ~~“cancel”~~ and abort these steps. (For example if the user cancels the request.)		# Optionally asynchronously fail with the reason "cancel" and abort these steps. (For example if the user cancels the request.)
	# For each tuple in the autofill set:		# For each tuple in the autofill set:
	#: a. Skip this tuple if the input’s attribute value for autocomplete is different than the one stored in the tuple.		#: a. Skip this tuple if the input’s attribute value for autocomplete is different than the one stored in the tuple.
Line 59:		Line 59:
	# Set the requestAutocompleteIsActive flag to false.		# Set the requestAutocompleteIsActive flag to false.

	When the user agent is said to asynchronously fail with a reason it queue an event to fire on the form element currently being operated on of a new AutocompleteErrorEvent with the type ~~“autocompleteerror”~~ and the reason specified.		When the user agent is said to asynchronously fail with a reason it queue an event to fire on the form element currently being operated on of a new AutocompleteErrorEvent with the type "autocompleteerror" and the reason specified.

	[[Category:Proposals]]		[[Category:Proposals]]