:read-write CSS pseudo-class shouldn't match disabled input/textarea

By design Issue #7226201

Details

Author
Chris R.
Created
Apr 16, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
  • Chrome
Found in build #
13.10586
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

  1. Open the attached testcase in Edge.
  2. Observe the background colors of the <textarea>s and <input>s.
    What is the expected behavior?
    The <textarea>s and <input>s should have white backgrounds.
    What went wrong?
    The <textarea>s and <input>s have red backgrounds, indicating that :read-write matched the disabled <input>s and disabled <textarea>s.

Attachments

Comments and activity

  • Per https://html.spec.whatwg.org/multipage/scripting.html#selector-read-write , :read-write should match:

    • `` elements […] that are mutable (i.e. that […] and that are not disabled)
    • `` elements that […], and that are not disabled

    Thus, :read-write shouldn’t be matching the disabled s and disableds in the testcase.

  • Microsoft Edge Team

    Changed Status to “By design”

  • Okay, I totally understand how https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/7229941/ is objectionable, but I don’t see how the behavior in this bug (7226201; :read-write matching disabled elements, which the user cannot interact with and are thus NOT writeable) could be seen as sensible.
    Could you give your reasoning for why this is "By design"?

  • This also happens in Chrome. Not sure why we should say the textarea is readonly, it is only disabled. This is not semantically the same thing. If you believe this is a bug both Chrome and Edge share, could you please point out to the spec section that describes your behavior as correct?

    Best,
    MS Edge Team

You need to sign in to your Microsoft account to add a comment.

Sign in