448111 Wrong float placement in pseudo cell in table with <script>

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1The columns of page are not coming properly.Same website works fine when viewed in Firefox 2.16(and earlier) and IE7.CSS and everything is same so probably there is a bug in page rendering of FF 3.0.1.Reproducible: AlwaysSteps to Reproduce:3.

Severity: normal minorComponent: General Layout: TablesKeywords: regression,testcaseProduct: Firefox CoreQA Contact: general layout.tablesHardware: PC AllSummary: Page rendering problem Wrong float placement in pseudo cell in table with script Version: unspecified 1.9.0 Branch
Thank you so much Mats, Can you please tell me what can i do to remove this problem?
is there anything else need to be changed? I hope layout wont break or messed up?waiting for reply.Regards,Ajay

I don"t know. I guess you have to try and see if the result is what you want.

thanks a lot...!Status: UNCONFIRMED RESOLVEDClosed: 12 years agoResolution: --- FIXED

No problem, but we still need to fix the layout bug in our code as thetestcase demonstrates.

Status: RESOLVED UNCONFIRMEDResolution: FIXED ---

(In reply to comment #7) No problem, but we still need to fix the layout bug in our code as the testcase demonstrates.
Yes, Coz my layout worked in IE and FF2.XX so i thought might be bug in 3.0Still thanks to you. for all your help.

Status: UNCONFIRMED RESOLVEDClosed: 12 years ago 12 years agoResolution: --- FIXED

It *is* a bug in Firefox. By removing "float" your site doesn"t trigger thebug anymore, but the bug is still there in Firefox and we need to fix that,and that work is what this bug report is tracking.

Status: RESOLVED UNCONFIRMEDResolution: FIXED ---

Fixed by checkin for bug 148810. Added tests.

Assignee: nobody bzbarskyStatus: NEW RESOLVEDClosed: 12 years ago 11 years agoFlags: in-testsuite+Resolution: --- FIXED You need to log in before you can comment on or make changes to this bug.