After landing of reflow_branch patch appears next collisions on page http://www.mtv.de/kino/index.php STEPS LEADING TO PROBLEM: 1. Go to the http://www.mtv.de/kino/index.php 2. scroll page to the middle EXPECTED OUTCOME: Page should be displayed properly. ACTUAL OUTCOME: There are additional green backgrounds on the right side of the page. They are displayed between the middle part and the right part of the page. See screenshots in attachments

A <table width="424"> is 424px wide in a non-reflow-branch build and 456px wide in a reflow branch one. Testcase would help.

I'm not sure how useful this is, I reduced this from the MTV.com page. It does show a difference between trunk before reflow branch landing and after. In the post-reflow-landing build, the table is 588px wide, in my pre-reflow-landing build (trunk 2006-12-04) the table is 310px wide.

Filed bug 363150 on that testcase; the patch there fixes it but not this bug or bug 363144... so once that lands we can try reducing again.

I applied the patch for bug 363150 and tried to reduce this testcase again. As with the previous testcase, I'm not sure that this is the only cause of the layout problem on that site, but it shows more differences between builds from before and after the reflow branch landing. 1) getComputedStyle for the tables is broken and always returns the width of the viewport (more than likely a seperate bug) 2) The first table is a few pixels smaller in a pre-reflow branch landing build (two distinct background "sections" vs. 3)

Yeah, getComputedStyle is a separate bug. Get it filed and cc me? I can try to fix it tonight, but I have a plane to catch right now...

I filed bug 363183 for the getComputedStyle part.

Bug 363150 fixed, but all other bugs related to mtv.de still reproducable.. Also table "KINO CHARTS" in URL page, also looks very bad.

*** This bug has been marked as a duplicate of 363329 ***

Bug 363329 fixes the page, although both testcases are still broken. However, separate bugs have been filed on both of them, so that seems ok.

This seems to be covered by other bugs/tests.