User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0 Page has a table cell containing an OBJECT for some Flash content. The height for this OBJECT is set to 295 px. In FF3.0 RC1 the height for the table cell becomes 298 px, as shown by DOM inspector. This messes up the rendering of this page, as seen bij the horizontal blue line above the heading: http://www.oranjecasino.com This is a regression as earlier released versions (FF 1 and 2) render the page correctly, as do MSIE 6 and 7. Reproducible: Always Steps to Reproduce: 1. Go to http:/www.oranjecsino.com 2. 3. Actual Results: Height of table cell containing Flash OBJECT becomes 298 px, horizontal blue line appearing above text heading. Expected Results: Height of table cell containing Flash OBJECT should be 295 px, no horizontal blue line appearing. Page is rendered in quirks mode, which is expected.
Version: unspecified → 3.0 Branch
Confirmed on Windows XP. Regression range is: http://bonsai.mozilla.org/cvsquery.cgi?module=PhoenixTinderbox&date=explicit&mindate=1172169480&maxdate=1172176319
Component: General → Layout: Tables
Product: Firefox → Core
QA Contact: general → layout.tables
Version: 3.0 Branch → Trunk
I'm not seeing a horizontal blue line (on Linux), unless I'm looking in the wrong place. A testcase would be useful.
Created attachment 321488 [details] screenshot Weel, it's quite obvious on Win XP, see attached screenshot. But I'll try to create a testcase.
Created attachment 321494 [details] testcase Here's a minimal testcase. It alerts with the ClientHeight of the cell, which should be 295. The bug appears to be caused by the newlines around the EMBED within the OBJECT: if I remove those, I get 295. Also, if you enlarge the font-size in the style defined for the table, the clientHeight of the cell becomes even bigger.
Please note that the site mentioned above has been updated since the release of FF 3.0 to work around the bug, so please refer to the testcase to reproduce this bug.
You need to log in before you can comment on or make changes to this bug.