From f7352c7c5a45026f64a6dfbc61a3ac7366e8629f Mon Sep 17 00:00:00 2001 From: Kagami Sascha Rosylight Date: Mon, 17 Aug 2020 19:01:32 +0200 Subject: [PATCH] Remove mutability check from legacy activation behaviors This is a followup to #5805, removing some now-redundant checks while fixing the condition introduced there to be a bit less far-reaching. (In particular, we want disabled checkboxes and radio buttons to still be immutable, even if that doesn't impact their activation behavior.) --- source | 15 +++++---------- 1 file changed, 5 insertions(+), 10 deletions(-) diff --git a/source b/source index 0e39db01334..be7df61908e 100644 --- a/source +++ b/source @@ -44700,9 +44700,8 @@ interface HTMLInputElement : HTMLElement { agent should not allow the user to modify the element's value or checkedness.

-

When an input element is disabled and - is not in the Checkbox nor Radio states, it is not When an input element is disabled, it is not mutable.

The readonly attribute can also in some @@ -44720,9 +44719,9 @@ interface HTMLInputElement : HTMLElement {

The activation behavior for input elements are these steps:

    -
  1. If this element is not mutable and is not in Checkbox nor - Radio, then return.

  2. +
  3. If this element is not mutable and is not in the Checkbox state and is not in the Radio state, then return.

  4. Run this element's input activation behavior, if any, and do nothing otherwise.

  5. @@ -44732,8 +44731,6 @@ interface HTMLInputElement : HTMLElement { steps:

      -
    1. If this element is not mutable, then return.

    2. -
    3. If this element's type attribute is in the Checkbox state, then set this element's checkedness to its opposite value (i.e. true if it is false, @@ -44751,8 +44748,6 @@ interface HTMLInputElement : HTMLElement { steps:

        -
      1. If the element is not mutable, then return.

      2. -
      3. If the element's type attribute is in the Checkbox state, then set the element's checkedness and the element's