WHATWG Wiki - User contributions [en]

RequestAutocomplete

2014-04-04T01:30:37Z

Dbeam:

requestAutocomplete proposed spec (as implemented in Chromium)

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 (http://crbug.com/343630).

== Interfaces Additions==

interface '''HTMLFormElement''' : HTMLElement {
...
void requestAutocomplete();
};

enum AutoCompleteErrorReason {
"",
"cancel",
"disabled",
"invalid"
};

[Constructor(DOMString type, optional AutocompleteErrorEventInit eventInitDict)]
interface '''AutocompleteErrorEvent''' : Event {
readonly attribute AutoCompleteErrorReason reason;
};

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

== Algorithms ==

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 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.
#: (For example the user agent may give the user an option to ignore all autocomplete requests.)
# Set the ''requestAutocompleteIsActive'' flag to true.
# Let the pending autofill set be an empty set of autocomplete tuples of the form
#: ( autocomplete attribute: string, input: Element )
# For each element that has this form element as its form owner add it to the pending autocomplete set with its attribute values if:
#* The autocomplete attribute is specified for its element type.
#* The autocomplete attribute parses to a valid value.
# Asynchronously request autocomplete from the user agent for the pending auto fill set for this form element.

When the user agent is said to request autocomplete for a form element it should run the following steps:

# 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.)
# 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.
#: 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.
# Statically validate the constraints and:
#: a. If the result is negative asynchronously fail with the reason "invalid".
#: b. If the result is positive fire a simple event named "autocomplete" that bubbles on the form element.
# Set the requestAutocompleteIsActive flag to false.

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]]

RequestAutocomplete

2014-04-04T01:29:22Z

Dbeam:

requestAutocomplete proposed spec (as implemented in Chromium)

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 (http://crbug.com/343630).

== Interfaces Additions==

interface '''HTMLFormElement''' : HTMLElement {
...
void requestAutocomplete();
};

enum AutoCompleteErrorReason {
"",
"cancel",
"disabled",
"invalid"
};

[Constructor(DOMString type, optional AutocompleteErrorEventInit eventInitDict)]
interface '''AutocompleteErrorEvent''' : Event {
readonly attribute AutoCompleteErrorReason reason;
};

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

== Algorithms ==

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 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.
#: (For example the user agent may give the user an option to ignore all autocomplete requests.)
# Set the ''requestAutocompleteIsActive'' flag to true.
# Let the pending autofill set be an empty set of autocomplete tuples of the form
#: ( autocomplete attribute: string, input: Element )
# For each element that has this form element as its form owner add it to the pending autocomplete set with its attribute values if:
#* The autocomplete attribute is specified for its element type.
#* The autocomplete attribute parses to a valid value.
# Asynchronously request autocomplete from the user agent for the pending auto fill set for this form element.

When the user agent is said to request autocomplete for a form element it should run the following steps:

# 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.)
# 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.
#: 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.
# Statically validate the constraints and:
#: 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.
# 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.

[[Category:Proposals]]

RequestAutocomplete

2014-04-04T01:29:01Z

Dbeam:

requestAutocomplete proposed spec (as implemented in Chromium)

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 (http://crbug.com/343630).

== Interfaces Additions==

interface '''HTMLFormElement''' : HTMLElement {
...
void requestAutocomplete();
};

enum AutoCompleteErrorReason {
"",
"cancel",
"disabled",
"invalid"
};

[Constructor(DOMString type, optional AutocompleteErrorEventInit eventInitDict)]
interface '''AutocompleteErrorEvent''' : Event {
readonly attribute AutoCompleteErrorReason reason;
};

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

== Algorithms ==

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 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.
#: (For example the user agent may give the user an option to ignore all autocomplete requests.)
# Set the ''requestAutocompleteIsActive'' flag to true.
# Let the pending autofill set be an empty set of autocomplete tuples of the form
#: ( autocomplete attribute: string, input: Element )
# For each element that has this form element as its form owner add it to the pending autocomplete set with its attribute values if:
#* The autocomplete attribute is specified for its element type.
#* The autocomplete attribute parses to a valid value.
# Asynchronously request autocomplete from the user agent for the pending auto fill set for this form element.

When the user agent is said to request autocomplete for a form element it should run the following steps:

# 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.)
# 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.
#: 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.
# Statically validate the constraints and:
#: 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.
# 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.

[[Category:Proposals]]

RequestAutocomplete

2014-04-04T01:28:26Z

Dbeam:

requestAutocomplete proposed spec (as implemented in Chromium)

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 (http://crbug.com/343630).

== Interfaces Additions==

interface '''HTMLFormElement''' : HTMLElement {
...
void requestAutocomplete();
};

enum AutoCompleteErrorReason {
"",
"cancel",
"disabled",
"invalid"
};

[Constructor(DOMString type, optional AutocompleteErrorEventInit eventInitDict)]
interface '''AutocompleteErrorEvent''' : Event {
readonly attribute AutoCompleteErrorReason reason;
};

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

== Algorithms ==

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 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.
#: (For example the user agent may give the user an option to ignore all autocomplete requests.)
# Set the ''requestAutocompleteIsActive'' flag to true.
# Let the pending autofill set be an empty set of autocomplete tuples of the form
#: ( autocomplete attribute: string, input: Element )
# For each element that has this form element as its form owner add it to the pending autocomplete set with its attribute values if:
#* The autocomplete attribute is specified for its element type.
#* The autocomplete attribute parses to a valid value.
# Asynchronously request autocomplete from the user agent for the pending auto fill set for this form element.

When the user agent is said to request autocomplete for a form element it should run the following steps:

# 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.)
# 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.
#: 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.
# Statically validate the constraints and:
#: 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.
# 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.

[[Category:Proposals]]

RequestAutocomplete

2014-04-02T21:59:02Z

Dbeam:

requestAutocomplete proposed spec (as implemented in Chromium)

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 (http://crbug.com/343630).

== Interfaces Additions==

interface '''HTMLFormElement''' : HTMLElement {
...
void requestAutocomplete();
};

enum AutoCompleteErrorReason {
"",
"cancel",
"disabled",
"invalid"
};

[Constructor(DOMString type, optional AutocompleteErrorEventInit eventInitDict)]
interface '''AutocompleteErrorEvent''' : Event {
readonly attribute AutoCompleteErrorReason reason;
};

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

== Algorithms ==

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 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.
#: (For example the user agent may give the user an option to ignore all autocomplete requests.)
# Set the ''requestAutocompleteIsActive'' flag to true.
# Let the pending autofill set be an empty set of autocomplete tuples of the form
#: ( autocomplete attribute: string, input: Element )
# For each element that has this form element as its form owner add it to the pending autocomplete set with its attribute values if:
#* The autocomplete attribute is specified for its element type.
#* The autocomplete attribute parses to a valid value.
# Asynchronously request autocomplete from the user agent for the pending auto fill set for this form element.

When the user agent is said to request autocomplete for a form element it should run the following steps:

# 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.)
# 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.
#: 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.
# Statically validate the constraints and:
#: 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.
# 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.

[[Category:Proposals]]

RequestAutocomplete

2013-03-23T00:09:58Z

Dbeam: /* Interfaces Additions */

requestAutocomplete proposed spec (as implemented in Chromium)

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.

== Interfaces Additions==

interface '''HTMLFormElement''' : HTMLElement {
...
void requestAutocomplete();
};

enum AutoCompleteErrorReason {
"cancel",
"disabled",
"invalid"
};

[Constructor(DOMString type, optional AutocompleteErrorEventInit eventInitDict)]
interface '''AutocompleteErrorEvent''' : Event {
readonly attribute AutoCompleteErrorReason reason;
};

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

== Algorithms ==

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 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.
#: (For example the user agent may give the user an option to ignore all autocomplete requests.)
# Set the ''requestAutocompleteIsActive'' flag to true.
# Let the pending autofill set be an empty set of autocomplete tuples of the form
#: ( autocomplete attribute: string, input: Element )
# For each element that has this form element as its form owner add it to the pending autocomplete set with its attribute values if:
#* The autocomplete attribute is specified for its element type.
#* The autocomplete attribute parses to a valid value.
# Asynchronously request autocomplete from the user agent for the pending auto fill set for this form element.

When the user agent is said to request autocomplete for a form element it should run the following steps:

# 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.)
# 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.
#: 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.
# Statically validate the constraints and:
#: 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.
# 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.

[[Category:Proposals]]