RESOLVED CONFIGURATION CHANGED 56907
Incorrect rendering of the CSS adjacent selectors in Webkit/534.16 (Chrome 10)
https://bugs.webkit.org/show_bug.cgi?id=56907
Summary Incorrect rendering of the CSS adjacent selectors in Webkit/534.16 (Chrome 10)
Ilya (SelenIT)
Reported 2011-03-23 01:44:09 PDT
Created attachment 86588 [details] simple demo, based on code example from http://htmlbook.ru/samcss/sosednie-selektory In Webkit/534.16 (Chrome 10, Chromium) the adjacent CSS selectors are rendered in an unexpected way: the corresponding style applies not only to the matching element, but also to all elements of the same tag name and class name till the end of the document. However, the document inspector from Developer Tools reports that these elements have correct style, so the bug is only visual. In the attached example (based on the code example from http://htmlbook.ru/samcss/sosednie-selektory in which the bug was first noticed) only the I element in the second P is expected to be red because only this paragraph contains I element preceded by B element (which should match the "B + I" CSS selector). But in fact the I element in the third paragrpaph is red, too (although there is no B element in that paragraph at all). Webkit/533.20.25 (Safari 5 for Windows) renders this example correctly.
Attachments
simple demo, based on code example from http://htmlbook.ru/samcss/sosednie-selektory (635 bytes, text/html)
2011-03-23 01:44 PDT, Ilya (SelenIT)
no flags
ChangSeok Oh
Comment 1 2011-03-28 01:21:36 PDT
(In reply to comment #0) > Created an attachment (id=86588) [details] > simple demo, based on code example from http://htmlbook.ru/samcss/sosednie-selektory > > In Webkit/534.16 (Chrome 10, Chromium) the adjacent CSS selectors are rendered in an unexpected way: the corresponding style applies not only to the matching element, but also to all elements of the same tag name and class name till the end of the document. However, the document inspector from Developer Tools reports that these elements have correct style, so the bug is only visual. > > In the attached example (based on the code example from http://htmlbook.ru/samcss/sosednie-selektory in which the bug was first noticed) only the I element in the second P is expected to be red because only this paragraph contains I element preceded by B element (which should match the "B + I" CSS selector). But in fact the I element in the third paragrpaph is red, too (although there is no B element in that paragraph at all). > > Webkit/533.20.25 (Safari 5 for Windows) renders this example correctly. I couldn't reproduce this issue on r82088, Safari 5.0.4 and Chrome 12.0.712.0 dev.
ChangSeok Oh
Comment 2 2011-03-28 01:22:17 PDT
(In reply to comment #0) > Created an attachment (id=86588) [details] > simple demo, based on code example from http://htmlbook.ru/samcss/sosednie-selektory > > In Webkit/534.16 (Chrome 10, Chromium) the adjacent CSS selectors are rendered in an unexpected way: the corresponding style applies not only to the matching element, but also to all elements of the same tag name and class name till the end of the document. However, the document inspector from Developer Tools reports that these elements have correct style, so the bug is only visual. > > In the attached example (based on the code example from http://htmlbook.ru/samcss/sosednie-selektory in which the bug was first noticed) only the I element in the second P is expected to be red because only this paragraph contains I element preceded by B element (which should match the "B + I" CSS selector). But in fact the I element in the third paragrpaph is red, too (although there is no B element in that paragraph at all). > > Webkit/533.20.25 (Safari 5 for Windows) renders this example correctly. I couldn't reproduce this issue on r82088, Safari 5.0.4 and Chrome 12.0.712.0 dev.
Brent Fulgham
Comment 3 2022-07-12 14:28:58 PDT
Safari, Chrome, and Firefox all agree on rendering for this test case. I don't believe there is any remaining compatibility issue.
Note You need to log in before you can comment on or make changes to this bug.