diff --git a/source b/source index a92a00a0afb..5664e03e9ee 100644 --- a/source +++ b/source @@ -47817,11 +47817,11 @@ ldh-str = < as defined in selected files.

-

The element's input activation behavior is to run the following steps:

+

The input activation behavior for such an element element is:

    -

  1. If the algorithm is invoked when the element's Window object does not have - transient activation, then return without doing anything else.

    2. +

  2. If the algorithm is invoked when element's relevant global object + does not have transient activation, then return.

  3. Run these steps in parallel:

    @@ -47830,15 +47830,33 @@ ldh-str = < as defined in     multiple attribute is not set, there must be no more than - one file selected; otherwise, any number may be selected. Files can be from the filesystem or - created on the fly, e.g., a picture taken from a camera connected to the user's - device.

    4. + data-x="attr-input-multiple">multiple attribute is not set on element, there + must be no more than one file selected; otherwise, any number may be selected. Files can be + from the filesystem or created on the fly, e.g., a picture taken from a camera connected to the + user's device.

  4. Wait for the user to have made their selection.

    5. -

  5. Update the file selection for the input element.

    6. +

  6. If the user dismissed the prompt without changing their selection, then queue an + element task on the user interaction task source given element + to fire an event named cancel at element, with the bubbles attribute initialized to true.

    7. + +

  7. Otherwise, update the file selection for element.

+ +

As with all user interface specifications, user agents have a good deal of + freedom in how they interpret these requirements. The above text implies that a user either + dismisses the prompt or changes their selection; exactly one of these will be true. But the + mapping of these possibilities to specific user interface elements is not mandated by the + standard. For example, a user agent might interpret clicking the "Cancel" button when files were + previously selected as a change of selection to select zero files, thus firing input and change. Or it might + interpret such a click as a dismissal that leaves the selection unchanged, thus firing cancel. Similarly, it's up to the user agent whether re-selecting + the same files counts as were previously selected counts as a dismissal, or as a change of + selection.

@@ -123468,8 +123486,8 @@ INSERT INTERFACES HERE cancel Event - dialog elements - Fired at dialog elements when they are canceled by the user (e.g. by pressing the Escape key) + dialog elements, input elements + Fired at dialog elements when they are canceled by the user (e.g., by pressing the Escape key), or at input elements in the File state when the user does not change their selection change