Bug 239868

Created attachment 458545 [details] Test page showing the issue where :has() is not triggering a update While using the pseudo class selector :has() in combination with the ::after pseudo-element and passing a selector to the :has that contains the :empty pseudo class I get a flaky behavior where making a change that would make the selector passed to the :has() be invalid does not actually invalidate the selector that has the :has() resulting in a flaky behavior. To see the behavior in action on the attached test page do the following steps: 1. Click on the add child button 1.1. You should see a child that is not empty and has a random number or, 1.2. A child that has no content and the text "::after text" is displayed from the ::after element on the parent 2. If you got a empty child now click on the add text button Expected: The child is now not empty therefore the selector ".parent:has(.child:only-child:empty)::after" is invalid and the "::after text" should disappear from the parent element Currently: The "::after text" is still present on the parent and has no selector matching it