[Webkit-unassigned] [Bug 62754] [chromium] new CSS 2.1 layout tests failing

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=62754





--- Comment #3 from Nikolas Zimmermann <zimmermann at kde.org>  2011-06-16 00:41:17 PST ---
(In reply to comment #0)
> The following (new) layout tests are giving incorrect pixel results on Chromium after WebKit r88913:
> 
> WIN LINUX : css2.1/20110323/block-non-replaced-width-008.htm = IMAGE+TEXT
> - big red square visible (should be no red)
> WIN LINUX : css2.1/20110323/block-replaced-width-001.htm = IMAGE+TEXT *
> - blue box is offset from the orange box
> WIN LINUX : css2.1/20110323/replaced-elements-001.htm = IMAGE+TEXT
> - orange box should be horizontally centered; are left-justified
> WIN LINUX : css2.1/20110323/replaced-intrinsic-ratio-001.htm = IMAGE+TEXT
> - should have six blue squares; only four are visible (the rest would probably be visible except the window is too small)
> 
> The pixel results on Safari/mac are wrong as well, except for the *'ed test above, which is only incorrect on Chromium.  The rest of the new test results seem to be ok.

I've verified these tests on a trunk build on SnowLeopard.
1. replaced-intrinsic-ratio-001.htm
It has six blue squares, it's just that the DRT dump doesn't show all of them as the size of the document is larger than the 800x600 (at least in height). If you manually run it, you'll see all of them work fine.
This test also has duplicates in svg/zoom/page/zoom-replaced-intrinsic-ratio-001.htm which zooms the test out 4 times, so that the full output (6 blue squares) fits into the DRT dumped image, so that's covered as well.

2. block-replaced-width-001.htm
Works just fine for me? No offset: the orange box is right above the blue box, no gaps.

3. block-non-replaced-width-008.htm
As reported in the original bug report (15849) this is still failing. It failed before my patch and still fails now, as its unrelated to the intrinsic sizing work.

4. replaced-elements-001.htm
Good catch, but I just checked it was broken before as well. I forgot to mention it in the bug report 15849, where I added these tests.

Can you confirm Chromium behaves the same, or does it still have a chromium specific bug on any of those?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.