Bug 53819

Summary: REGRESSION: CSS declarations in a rule with next sibling selector affects other elements
Product: WebKit Reporter: Simon Pieters (:zcorpan) <zcorpan>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: aestes
Priority: P2 Keywords: InRadar, Regression
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
URL: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/826

Simon Pieters (:zcorpan)
Reported 2011-02-04 15:16:28 PST
Chrome Version : 10.0.648.18 (Official Build 73584) dev URLs (if applicable) : http://software.hixie.ch/utilities/js/live-dom-viewer/saved/826 Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari 5: PASS Firefox 3.x: dunno, but Firefox 4 (trunk) is PASS IE 7/8: dunno (Opera 11 is PASS, and reportedly Chrome 9 is also PASS) What steps will reproduce the problem? 1. Use a sibling selector like .a + p { clear:left } 2. Use markup like <div class=a></div><p></p><div class=b>foo</div><p>bar</p> 3. What is the expected result? The "bar" paragraph should not get the 'clear:left' style applied. What happens instead? The "bar" paragraph gets the 'clear:left' style applied. Devtools shows 'clear:left' among the inherited styles for the element. Please provide any additional information below. Attach a screenshot if possible. chromium bug at http://code.google.com/p/chromium/issues/detail?id=72005
Attachments
Alexey Proskuryakov
Comment 1 2011-02-04 19:26:10 PST
Andy Estes
Comment 2 2011-02-05 17:14:17 PST
I can't reproduce this in the latest WebKit nightly build (r77734). Simon, are you able to?
Andy Estes
Comment 3 2011-02-05 17:23:57 PST
'bisect-builds -p' tells me: Fails: r77618 Works: r77709 Unfortunately I don't have time right now to narrow it down any further.
Andy Estes
Comment 4 2011-02-05 17:44:00 PST
Ahh, found it. Fixed by http://trac.webkit.org/changeset/77664. *** This bug has been marked as a duplicate of bug 53610 ***
Note You need to log in before you can comment on or make changes to this bug.