MS Edge does not recalculate style for :disabled pseudo-class followed by sibling combinator

Issue #11295231 • Assigned to Bogdan B.


Ron O.
Mar 16, 2017
This issue is public.
Found in
  • Microsoft Edge
Standard affected
Selectors Level 3

Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Given a CSS rule that uses a :disabled pseudo-class followed by a sibling combinator such as input:disabled + span, MS Edge fails to properly recalculate and re-apply updated styles to the sibling (span in the given example) element when the element to which the :disabled pseudo-class is applied, toggles its disabled state.

Minimal reproducing test case

Known workaround

A known workaround is to have another CSS rule that uses the disabled attribute followed by a sibling combinator. This rule can be empty (no properties) and can even target a completely non-existant type of element. It just needs to be there.

A minimal sufficient rule to avoid the issue from occuring anywhere in the loaded document is: [disabled] ~ _ {}


0 attachments

    Comments and activity

    • Changed Steps to Reproduce

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

      Changed Assigned To to “Bogdan B.”

      Changed Assigned To from “Bogdan B.” to “Kevin B.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Kevin B.” to “Bogdan B.”

      Changed Status from “Confirmed” to “Won’t fix”

      Changed Status from “Won’t fix”

    • Reactivating auto-resolved valid bugs reported by web dev community. Those were not expected to be resolved. We apologize for any inconvenience!

    • Microsoft Edge Team

      Changed Assigned To to “Bogdan B.”

    • Just stumbled across this issue today myself. I noticed the fiddle used to demonstrate the issue is gone, so here’s my version:

      The background on the label should be red when the page loads, but does not change color until you hover over the label. Thankfully Ron’s workaround does fix the issue until the Edge team fixes the bug. I’m on EdgeHTML 17.17134.

    • Is there any update on this? The bug is causing problems for my team as well.

      Here is the GitHub issue:

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

    Sign in