Sibling elements not invalidated on "style" attribute update and selector [style*="..."]

Fixed Issue #10145497


Ilpo O.
Dec 9, 2016
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Fixed in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

When using the selector [style*="block"] + element, Edge doesn’t update its styles when js changes the display value of the preceding element. However, using js to change other attributes does work with a similar selector.
Both buttons should toggle the blur for the #b element (as they do in Chrome). However, in Edge, only the second button toggles the blur. If you click on the first button, then inspect the #b element, it updates the styles and becomes blurred.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Status

    • Thank you for the report. I believe we’ve found this recent regression and fixed it in internal version. You should be able to verify the fix in the public Insider Preview builds early next year.

    • Changed Status

    • I’m on 15.15063 and the bug still persists. Tested on both computer and W10 mobile (slow insider ring). It doesn’t seem like the Creators’ Update fixed this at all.

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

      Changed Title from “Styles don't update” to “Sibling elements not invalidated on "style" attribute update and selector [style*="..."]”

      Changed Assigned To to “Kevin B.”

      Changed Status to “Confirmed”

    • Looks like this case isn’t fixed indeed.

    • Thank you for reporting the issue. As it turns out one particular case was missed - inline style changes and [style] attribute matching. This should now be fixed as well - really appreciate extra verification here, that allowed us to step back and reevaluate the issue. You should expect to see this fixed in one of the coming Windows insider Preview builds (for real this time ;-)).

    • Microsoft Edge Team

      Changed Status from “Confirmed” to “Fixed”

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

    Sign in