Summary: | :empty still matches after content is added to element with display: none | ||
---|---|---|---|
Product: | WebKit | Reporter: | webkit |
Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | ap, davidbarr, jchaffraix, simon.fraser |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://jsfiddle.net/gtXYC/1/ |
Description
webkit
2011-12-28 00:22:00 PST
Verified as fixed with WebKit Nightly Version 5.1.5 (6534.55.3, r115022). (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? 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. $ 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 *** This bug has been marked as a duplicate of bug 79734 *** Thank you for researching when this got fixed! |