diff --git a/source b/source index b8a0cef9a14..7e485fe18cf 100644 --- a/source +++ b/source @@ -48198,6 +48198,35 @@ interface HTMLInputElement : HTMLElement { data-x="attr-input-type-checkbox">Checkbox state) stop an input element from being mutable.

+

The input element can support a picker. A + picker is a user interface element that allows the end user to choose a value. Whether an + input element supports a picker depends on the type attribute state and implementation-defined + behavior. An input element must support a picker when its type attribute is in the File + Upload state.

+ +
+

As of the time of this writing, typical browser implementations show such picker UI for:

+ + +
+

The cloning steps for input elements must propagate the value, dirty value flag,

input.showPicker()
-

Shows any applicable picker UI for input, so that the user can select a value. (If - no picker UI is implemented for the given control, then this method does nothing.)

+

Shows any applicable picker UI for input, so that the user can select a value.

+ +

If input does not support a picker, + this method does nothing.

Throws an "InvalidStateError" DOMException if input is not mutable.

@@ -53159,6 +53190,9 @@ You cannot submit this form when the field is incorrect.

  • Consume user activation given element's relevant global object.

    • +

  • If element does not support a + picker, then return.

    • +

  • If element is an input element and element's type attribute is in the

  • -

    Otherwise, the user agent should show any relevant user interface for selecting a value for - element, in the way it normally would when the user interacts with the control. (If - no such UI applies to element, then this step does nothing.)

    +

    Otherwise, the user agent should show the relevant user interface for selecting a value for + element, in the way it normally would when the user interacts with the control.

    -

    If such a user interface is shown, it must respect the requirements stated in the relevant +

    When showing such a user interface, it must respect the requirements stated in the relevant parts of the specification for how element behaves given its type attribute state. (For example, various sections describe restrictions on the resulting value string.)

    @@ -53213,33 +53246,6 @@ You cannot submit this form when the field is incorrect. firing either input and change events, or a cancel event.)

    - -
    -

    As of the time of this writing, typical browser implementations show such picker UI for:

    - -
      -

    • input elements whose type - attributes are in the Date, Month, Week, - Time, Local Date and Time, and Color states;

      • - -

    • input elements in various states that have a suggestions source element;

      • - -

    • input elements whose type attribute - is in the File Upload state (although those are - handled via the special case above, instead of by this step); and

      • - -

    • select elements.

      • -
    - -

    However, the intent of this step is to trigger any picker UI implementation. So - for example, if a user agent implemented a password picker UI for the Password state, then this method would be expected to - show that picker UI when called on a password input.

    -
    • @@ -75069,6 +75075,26 @@ Demos:

    The :volume-locked pseudo-class must match all media elements when the user agent's volume locked is true.

    + +
    :open
    +
    +

    The :open pseudo-class must match any + element falling into one of the following categories:

    + + +

    This specification does not define when an element matches the