75294 2011-12-28 00:22:00 -0800 :empty still matches after content is added to element with display: none 2012-04-26 22:37:46 -0700 1 1 1 Unclassified WebKit CSS 528+ (Nightly build) All All RESOLVED DUPLICATE 79734 http://jsfiddle.net/gtXYC/1/ P2 Normal --- 0 webkit webkit-unassigned ap davidbarr jchaffraix simon.fraser oldest_to_newest 527573 0 webkit 2011-12-28 00:22:00 -0800 Compare the following examples (using innerHTML to add content): 1) http://jsfiddle.net/gtXYC/0/ (works) 2) http://jsfiddle.net/gtXYC/1/ (broken) Same problem using appendChild() instead of innerHTML: 3) http://jsfiddle.net/gtXYC/2/ (works) 4) http://jsfiddle.net/gtXYC/3/ (broken) Examples 1/3: The div's background-color changes based on whether the div is empty or not. Examples 2/4: Same situation, except that the visibility of the div should change. The problem is that :empty still matches after content is added to the div. 610336 1 davidbarr 2012-04-25 21:43:20 -0700 Verified as fixed with WebKit Nightly Version 5.1.5 (6534.55.3, r115022). 610590 2 jchaffraix 2012-04-26 07:28:20 -0700 (In reply to comment #1) > Verified as fixed with WebKit Nightly Version 5.1.5 (6534.55.3, r115022). Are we sure the test cases attached on this bug are covered? Shouldn't we land them to prevent a regression? 610695 3 ap 2012-04-26 10:06:16 -0700 Since we don't know what fixed this, and haven't landed tests, this is WORKSFORME at best. I agree with Julien that we should investigate the need to land tests. 611167 4 davidbarr 2012-04-26 18:46:38 -0700 $ bisect-builds http://jsfiddle.net/gtXYC/1/ -r 109280:109476 -p -s Fails: r109280 Works: r109476 http://trac.webkit.org/log/trunk/?rev=109476&stop_rev=109281 See http://trac.webkit.org/changeset/109417/trunk :empty still applies to elements made non-empty via page dynamics. https://bugs.webkit.org/show_bug.cgi?id=79734 Covered by test: http://trac.webkit.org/browser/trunk/LayoutTests/fast/selectors/empty-element-made-non-empty.html?rev=109417 611169 5 davidbarr 2012-04-26 18:48:13 -0700 *** This bug has been marked as a duplicate of bug 79734 *** 611254 6 ap 2012-04-26 22:37:46 -0700 Thank you for researching when this got fixed!