First reaction -- what extensions do you have installed?

I have no extensions installed.

i think my bug is the same (there is a info about the version):
https://code.google.com/p/chromium/issues/detail?id=50214
the bug is still here with r53754

http://trac.webkit.org/changeset/63994 could be the problem.
("Updated table painting to draw cell layers in the correct order.")

 Issue 50214  has been merged into this issue.

fsamuel, can you take a look?

I'm working on it. I should have a patch out very soon.

Same on this https://code.google.com/p/chromium/issues/detail?id=50239

 Issue 50239  has been merged into this issue.

After reload, it can be fine sometimes but also can stay bad

here is an example with this page, see picture

and an other site for instance http://bichons-passion.forumpro.fr/forum.htm

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

This patch should fix this issue.

Having similar issue, but refresh doesn't seem to fix anything for me. It just seems to to display another cell incorrectly.

Good Example: http://img268.imageshack.us/img268/2921/chromiumtables.png

The issue the chunk of the render tree that is constructed before layout is non-deterministic. If the entire render tree is constructed before layout, then things will be fine. If not, things will be broken. I did not take this into account when I initially patched table rendering in webkit  bug 40775 . The patch I posted for webkit bug 42993 addresses this issue.

It appears the same bug I filled here:
https://code.google.com/p/chromium/issues/detail?id=50353

I did a little investigation, and it seems the things changed between 53616 and 53619 builds.

At first only vbulletin forums seemed affected, then I noticed the same layout corruption in other pages, even in code.google.com 

I confirm that a refresh doesn't fix anything. 

 Issue 50353  has been merged into this issue.

 Issue 50382  has been merged into this issue.

(Ironically the bug affects the bug page...)

The fix is coming: https://bugs.webkit.org/show_bug.cgi?id=42993

The fix does not seem very effective (see attached screenshots)

	TableRendering01.png 45.0 KB   View   Download

	TableRendering02.png 34.3 KB   View   Download

I forgot to specify the build: 6.0.478.0 (53895) Ubuntu 10.04

I don't think the fix has actually landed yet into WebKit.

This is a bad regression. Happens on Windows also with every page. reload fixes the problem.

 Issue 50536  has been merged into this issue.

 Issue 50458  has been merged into this issue.

Same problem here on kubuntu
6.0.478.0 (53895) Ubuntu 10.04

Just exactly when is this fix actually going to land and be included?
Build 54025 is still exhibiting the problem. I wouldn't mind so much except that it's getting tiresome to have half a screen of white space in my webmail account, and having to scroll way to the right and at other times having to deal with a column about 150 pixels wide because the content of tables is so badly skewed.

I apologize for the above comment #27, it looks like in build 54086 the table fix is in and working. 

seems to be fixed in chromium build 54084

(No comment was entered for this change.)

 Issue 50230  has been merged into this issue.

 Issue 50477  has been merged into this issue.

 Issue 50486  has been merged into this issue.

 Issue 50635  has been merged into this issue.

 Issue 50607  has been merged into this issue.

Verified in build: 7.0.517.36 beta
Platform: Win 7
Verified Fixed:Y
Unable to reproduce from any of the provided references, fix works

<b>What steps will reproduce the problem?</b>
Mac Chromium 6.0.477.0 (Developer Build 53676)

I don't have repro steps, but I've been seeing this a lot since I updated my copy of Chromium. Tables are being rendered incorrectly, with a cell's size being blown out. Reloading the page seems to fix it. I've attached 3 sample screen shots.

<b>What is the expected output? What do you see instead?</b>


<b>Please use labels and text to provide additional information.</b>

This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)