diff --git a/index b/index index 3382626f0d4..88df47ec05f 100644 --- a/index +++ b/index @@ -16,7 +16,7 @@

HTML 5

-

Draft Recommendation — 5 November 2008

+

Draft Recommendation — 6 November 2008

You can take part in this work. Join the working group's discussion list.

Web designers! We have a FAQ, a forum, and a help mailing list for you!

Multiple-page version:
@@ -24249,7 +24249,7 @@ function AddCloud(data, x, y) { ... } stepUp(), and stepDown() methods.

-

The input and change events do not fire.

+

The input and change events do not apply.

@@ -25508,7 +25508,8 @@ function AddCloud(data, x, y) { ... } value it had before the pre-click activation steps were run. The activation behavior is to fire a simple event called change at the - element.

+ element, then broadcast formchange events at the + element's form owner.

Constraint validation: If the element is required and its checkedness is false, then the element is suffering from being missing.

@@ -25613,7 +25614,8 @@ function AddCloud(data, x, y) { ... } the element's checkedness to false. The activation behavior is to fire a simple event called change - at the element.

+ at the element, then broadcast formchange events at the + element's form owner.

Constraint validation: If the element is required and all of the input elements in the radio button group have a @@ -25838,7 +25840,7 @@ function AddCloud(data, x, y) { ... } stepDown() and stepUp() methods.

-

The input and change events do not fire.

+

The input and change events do not apply.

@@ -25997,7 +25999,7 @@ function AddCloud(data, x, y) { ... } stepDown() and stepUp() methods.

-

The input and change events do not fire.

+

The input and change events do not apply.

@@ -26064,7 +26066,7 @@ function AddCloud(data, x, y) { ... } stepDown() and stepUp() methods.

-

The input and change events do not fire.

+

The input and change events do not apply.

@@ -26121,7 +26123,7 @@ function AddCloud(data, x, y) { ... } stepDown() and stepUp() methods.

-

The input and change events do not fire.

+

The input and change events do not apply.

@@ -26631,8 +26633,10 @@ You cannot complete this form until the field is correct.

When the input event applies, the user agent must queue a task to - fire a simple event called input at the input element - any time the user causes the element's value to change. User agents may + fire a simple event called input at the input element, + then broadcast forminput + events at the input element's form + owner, any time the user causes the element's value to change. User agents may wait for a suitable break in the user's interaction before queuing the task; for example, a user agent could wait for the user to have not hit a key for 100ms, so as to only fire the event when the user @@ -26642,8 +26646,10 @@ You cannot complete this form until the field is correct. if the element does not have an activation behavior defined but uses a user interface that involves an explicit commit action, then the user agent must queue a task to - fire a simple event called change at the input element - any time the user commits a change to the element's value or list of selected files.

+ fire a simple event called change at the input + element, then broadcast formchange events at the + input element's form owner, any time the + user commits a change to the element's value or list of selected files.

An example of a user interface with a commit action would be a File @@ -26660,7 +26666,7 @@ You cannot complete this form until the field is correct. and then dismissing the drop down would be a commit action.

In addition, when the change event applies, change events can also be fired as part - of the element's action behavior and as part of the + of the element's activation behavior and as part of the unfocusing steps.

The task source for these task is the user interaction task @@ -26886,15 +26892,17 @@ You cannot complete this form until the field is correct. should allow the user to pick an option element in its list of options that is itself not disabled. Upon this - option element being picked (either through a click, or + option element being picked (either through a click, or through unfocusing the element after changing its value, or through - any other mechanism), and before the relevant user interaction event - is queued (e.g. before the click + a menu command, or through any + other mechanism), and before the relevant user interaction event is + queued (e.g. before the click event), the user agent must set the selectedness of the picked option element to true and then queue a task to fire a simple event called change at the select element, using the user interaction task source as the - task source.

+ task source, then broadcast formchange events at the + element's form owner.

If the multiple attribute is absent, whenever an option element in the @@ -26917,16 +26925,19 @@ You cannot complete this form until the field is correct.

If the multiple attribute is present, and the element is not disabled, then the user agent - should allow the user to toggle the selectedness of the + should allow the user to toggle the selectedness of the option elements in its list of options that are - themselves not disabled. Upon the selectedness of one or + themselves not disabled + (either through a click, or through a menu command, or any other + mechanism). Upon the selectedness of one or more option elements being changed by the user, and before the relevant user interaction event is queued (e.g. before a related click event), the user agent must queue a task to fire a simple event called change at the select element, using the user interaction task - source as the task source.

+ source as the task source, then broadcast formchange events at the + element's form owner.

The reset algorithm for select elements is to go through @@ -28800,13 +28811,7 @@ interface HTMLOptionElement : tree order, fire a simple event named event name at the element. -

Still need to define when formchange and forminput - fire naturally.

- - - - -

4.11 Interactive elements

+

4.11 Interactive elements

4.11.1 The details element

@@ -31425,7 +31430,7 @@ menu li:not(:first-child)::before { content: ' | '; }

The Label of the command is the value of the option element's label attribute, if there is one, or the value of the option element's - textContent DOM attribute if it doesn't.

+ textContent DOM attribute if there isn't.

The Hint of the command is the string given by the element's title attribute, if any, and the empty @@ -31439,24 +31444,19 @@ menu li:not(:first-child)::before { content: ' | '; } otherwise.

The Disabled - State of the command is true (disabled) if the element has a - disabled attribute, and - false otherwise.

+ State of the command is true (disabled) if the element is + disabled or if its + nearest ancestor select element is disabled, and false + otherwise.

The Checked State - of the command is true (checked) if the element's selected DOM attribute is true, - and false otherwise.

+ of the command is true (checked) if the element's selectedness is true, and + false otherwise.

The Action of the - command depends on its Type. If the command is of Type "radio" then this must set - the selected DOM attribute - of the option element to true, otherwise it must toggle - the state of the selected - DOM attribute (set it to true if it is false and vice versa). Then - a change - event must be fired on the option element's - nearest ancestor select element (if there is one), as - if the selection had been changed directly.

+ command depends on its Type. If the command is of Type "radio" then it must pick the option + element. Otherwise, it must toggle the option + element.

4.11.6.5 Using the command element to define @@ -33314,11 +33314,6 @@ JSURL: http://ietfreport.isoc.org/all-ids/draft-hoehrmann-javascript-scheme-00.t values appropriately describing the state of the key input device at the time the event is created.

-

Firing a change event means that a change - event with no namespace, which bubbles but is not cancelable, and - which uses the Event interface, must be dispatched at - the given element.

-

Firing a contextmenu event means that a contextmenu event with no namespace, which bubbles and is cancelable, and which uses the @@ -39487,7 +39482,9 @@ at the first element with the given ID must be treated as if it was cloned and r element, and the element does not have a defined activation behavior, and the user has changed the element's value or its list of selected files while the control was focused without committing that change, then - fire a simple event called change at the element.

+ fire a simple event called change at the element, then + broadcast formchange + events at the element's form owner.

  • Unfocus the element.

    • diff --git a/source b/source index c36368fe97d..e654507e552 100644 --- a/source +++ b/source @@ -27084,7 +27084,7 @@ function AddCloud(data, x, y) { ... }

    The input and change events do not fire.

    + title="event-input-change">change events do not apply.

    @@ -28520,7 +28520,9 @@ function AddCloud(data, x, y) { ... } value it had before the pre-click activation steps were run. The activation behavior is to fire a simple event called change at the - element.

    + element, then broadcast formchange events at the + element's form owner.

    Constraint validation: If the element is required and its the element's checkedness to false. The activation behavior is to fire a simple event called change - at the element.

    + at the element, then broadcast formchange events at the + element's form owner.

    Constraint validation: If the element is required and all of the @@ -28896,7 +28900,7 @@ function AddCloud(data, x, y) { ... }

    The input and change events do not fire.

    + title="event-input-change">change events do not apply.

    @@ -29101,7 +29105,7 @@ function AddCloud(data, x, y) { ... }

    The input and change events do not fire.

    + title="event-input-change">change events do not apply.

    @@ -29175,7 +29179,7 @@ function AddCloud(data, x, y) { ... }

    The input and change events do not fire.

    + title="event-input-change">change events do not apply.

    @@ -29239,7 +29243,7 @@ function AddCloud(data, x, y) { ... }

    The input and change events do not fire.

    + title="event-input-change">change events do not apply.

    @@ -29895,8 +29899,10 @@ You cannot complete this form until the field is correct.

    When the input event applies, the user agent must queue a task to fire a simple event called input at the input element - any time the user causes the element's input at the input element, + then broadcast forminput + events at the input element's form + owner, any time the user causes the element's value to change. User agents may wait for a suitable break in the user's interaction before queuing the task; for example, a user agent could wait for the user to have @@ -29909,8 +29915,11 @@ You cannot complete this form until the field is correct. defined but uses a user interface that involves an explicit commit action, then the user agent must queue a task to fire a simple event called change at the input element - any time the user commits a change to the element's change at the input + element, then broadcast formchange events at the + input element's form owner, any time the + user commits a change to the element's value or list of selected files.

    @@ -29932,7 +29941,7 @@ You cannot complete this form until the field is correct.

    In addition, when the change event applies, change events can also be fired as part - of the element's action behavior and as part of the + of the element's activation behavior and as part of the unfocusing steps.

    The task source for these list of options that is itself not disabled. Upon this - option element being picked (either through a click, or + option element being picked (either through a click, or through unfocusing the element after changing its value, or through - any other mechanism), and before the relevant user interaction event - is queued (e.g. before the click + a menu command, or through any + other mechanism), and before the relevant user interaction event is + queued (e.g. before the click event), the user agent must set the selectedness of the picked option element to true and then queue a task to fire a simple event called change at the select element, using the user interaction task source as the - task source.

    + task source, then broadcast formchange events at the + element's form owner.

    If the multiple attribute is absent, whenever an option element in the @@ -30241,12 +30254,15 @@ You cannot complete this form until the field is correct.

    If the multiple attribute is present, and the element is not disabled, then the user agent - should allow the user to toggle the toggle the selectedness of the option elements in its list of options that are - themselves not disabled. Upon the disabled + (either through a click, or through a menu command, or any other + mechanism). Upon the selectedness of one or more option elements being changed by the user, and before the relevant user interaction event is queued (e.g. before a @@ -30254,7 +30270,9 @@ You cannot complete this form until the field is correct. agent must queue a task to fire a simple event called change at the select element, using the user interaction task - source as the task source.

    + source as the task source, then broadcast formchange events at the + element's form owner.

    The reset algorithm for select elements is to go through @@ -32601,9 +32619,6 @@ interface HTMLOptionElement : HTMLElement { -

    Still need to define when formchange and forminput - fire naturally.

    - @@ -35759,7 +35774,7 @@ menu li:not(:first-child)::before { content: ' | '; } is the value of the option element's label attribute, if there is one, or the value of the option element's - textContent DOM attribute if it doesn't.

    + textContent DOM attribute if there isn't.

    The Hint of the command is the string given by the element's otherwise.

    The Disabled - State of the command is true (disabled) if the element has a - disabled attribute, and - false otherwise.

    + State of the command is true (disabled) if the element is + disabled or if its + nearest ancestor select element is disabled, and false + otherwise.

    The Checked State - of the command is true (checked) if the element's selected DOM attribute is true, - and false otherwise.

    + of the command is true (checked) if the element's selectedness is true, and + false otherwise.

    The Action of the command depends on its Type. If the command is of Type "radio" then this must set - the selected DOM attribute - of the option element to true, otherwise it must toggle - the state of the selected - DOM attribute (set it to true if it is false and vice versa). Then - a change - event must be fired on the option element's - nearest ancestor select element (if there is one), as - if the selection had been changed directly.

    + title="command-facet-Type">Type "radio" then it must pick the option + element. Otherwise, it must toggle the option + element.

    Using the -

    Firing a change event means that a change - event with no namespace, which bubbles but is not cancelable, and - which uses the Event interface, must be dispatched at - the given element.

    -

    Firing a contextmenu event means that a contextmenu event with no @@ -44975,7 +44981,9 @@ at the first element with the given ID must be treated as if it was cloned and r title="concept-input-type-file-selected">selected files while the control was focused without committing that change, then fire a simple event called change at the element.

    + title="event-change">change     at the element, then + broadcast formchange + events at the element's form owner.

  • Unfocus the element.