diff --git a/source b/source index 2dec969bbf2..8ae1cd327bd 100644 --- a/source +++ b/source @@ -2972,6 +2972,7 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
  • currentTarget attribute
  • bubbles attribute
  • cancelable attribute
    • +
  • composed attribute
  • composed flag
  • isTrusted attribute
  • initEvent() method
    • @@ -45050,7 +45051,8 @@ interface HTMLInputElement : HTMLElement {

  • Queue an element task on the user interaction task source given the element to fire an event named input at the element, with the bubbles attribute initialized to true.

    • + data-x="dom-Event-bubbles">bubbles and composed + attributes initialized to true.

    @@ -47035,7 +47037,8 @@ ldh-str = < as defined in Fire an event named input at the element with the bubbles attribute initialized to true.

    + data-x="dom-Event-bubbles">bubbles and composed + attributes initialized to true.

  • Fire an event named change at the element with the Fire an event named input at the element with the bubbles attribute initialized to true.

    • + data-x="dom-Event-bubbles">bubbles and composed + attributes initialized to true.

  • Fire an event named change at the element with the selected - files so that it represents the user's selection.

    • - -

  • Fire an event named input at the input element, with the bubbles attribute initialized to true, and finally fire an event named change at the input element, with the bubbles attribute initialized to true.

    • - - +

  • Update the file selection for the input element.

    • If the element is mutable, the user agent should allow the - user to change the files on the list in other ways also, e.g. adding or removing files by - drag-and-drop. When the user does so, the user agent must queue an element task on - the user interaction task source given the input element to first update - the element's selected files so that it - represents the user's new selection, then fire an event - named input at the input element, with the bubbles attribute initialized to true, and finally fire an event named change - at the input element, with the bubbles - attribute initialized to true.

    + user to change the files on the list in other ways also, e.g., adding or removing files by + drag-and-drop. When the user does so, the user agent must update the file selection + for the element.

    If the element is not mutable, the user agent must not allow the user to change the element's selection.

    +

    To update the file selection for an element element:

    + +
      +
    1. +

      Queue an element task on the user interaction task source given + element and the following steps:

      + +
        +

      1. Update element's selected + files so that it represents the user's selection.

        2. + +

      2. Fire an event named input at the input element, with the bubbles and composed + attributes initialized to true.

        3. + +

      3. Fire an event named change at the input element, with the bubbles attribute initialized to true.

        4. +
      +
      2. +
    +

    Constraint validation: If the element is required and the list of selected files is empty, then the element is @@ -49361,12 +49366,12 @@ You cannot submit this form when the field is incorrect. queue an element task on the user interaction task source given the input element to fire an event named input at the input element, with the bubbles attribute initialized to true, and any time the user - commits the change, the user agent must queue an element task on the user - interaction task source given the input element to fire an event named change - at the input element, with the bubbles - attribute initialized to true.

    + data-x="dom-Event-bubbles">bubbles     and composed + attributes initialized to true, and any time the user commits the change, the user agent must + queue an element task on the user interaction task source given the + input element to fire an event named change at the input element, with the bubbles attribute initialized to true.

    An example of a user interface involving both interactive manipulation and a commit action would be a Range controls that use a @@ -49382,7 +49387,8 @@ You cannot submit this form when the field is incorrect. agent must queue an element task on the user interaction task source given the input element to first fire an event named input at the input element, with - the bubbles attribute initialized to true, and then bubbles and composed attributes initialized to true, and then fire an event named change at the input element, with the bubbles attribute initialized to true.

    @@ -49405,9 +49411,10 @@ You cannot submit this form when the field is incorrect. action, the user agent must queue an element task on the user interaction task source given the input element to fire an event named input at the input element, with - the bubbles attribute initialized to true. The - corresponding change event, if any, will be fired when the - control     loses focus.

    + the bubbles and composed attributes initialized to true. The corresponding + change event, if any, will be fired when the control loses focus.

    Examples of a user changing the element's value would include the user typing into a text control, pasting @@ -49434,7 +49441,8 @@ You cannot submit this form when the field is incorrect. task source given the input element to first update the value accordingly, then fire an event named input at the input element, with - the bubbles attribute initialized to true, then bubbles and composed attributes initialized to true, then fire an event named change at the input element, with the bubbles attribute initialized to true.

    @@ -49884,7 +49892,8 @@ interface HTMLSelectElement : HTMLElement {

    1. Fire an event named input at the select element, with the bubbles attribute initialized to true.

      2. + data-x="dom-Event-bubbles">bubbles and composed + attributes initialized to true.

    2. Fire an event named change at the select element, with the HTMLTextAreaElement : HTMLElement { element task on the user interaction task source given the textarea element to fire an event named input at the textarea element, with the bubbles attribute initialized to true. 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 pauses, instead of continuously for each keystroke.

      + data-x="dom-Event-bubbles">bubbles and composed + attributes initialized to true. 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 pauses, instead of continuously + for each keystroke.

      A textarea element's dirty value flag must @@ -50826,7 +50836,8 @@ interface HTMLTextAreaElement : HTMLElement {

    3. Queue an element task on the user interaction task source given the textarea element to fire an event named input at the textarea element, with the bubbles attribute initialized to true.

      4. + data-x="dom-Event-bubbles">bubbles and composed + attributes initialized to true.