User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030612 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030612 The above is another sample of a webpage which IE6 displays properly but Mozilla does not.. Likely (as with others) there is an html "error" which prevents this page from displaying properly. However, If IE6 ignores such errors and Mozilla does not display the page properly, which browser is a user likely to consider faulty? And.. which browser is a user likely to want to use? Reproducible: Always Steps to Reproduce: 1. 2.Load the above page. 3. Expected Results: If it was possibile to display a page properly EVEN IF it has some sort of common html error, Mozilla would be wise to do it so users will not get the idea that Mozilla is faulty (since IE6 seems to display such pages properly.) There are lots of examples of the above.
Let's at least pontificate in a category that might be correct for this bug. ->Layout for triage
Assignee: general → other
Component: Browser-General → Layout
QA Contact: general → ian
Created attachment 127709 [details] testcase <table width=1000> <tr><td width="100%"> <img src="something.gif" width=600><img src="something.gif" width=600> </td></tr> </table> the images wrap rather than expanding the width of the table. the images in the document (the top frame) are wider than the table's specified width. with the column width being specified as 100%, the table refuses to expand to accomodate the images without wrapping. in standards compliance mode, the images are always wrapped, even without the 100% column width.
reproduced with linux turnk 20030711. ==> tables
Assignee: other → table
Component: Layout → Layout: Tables
OS: Windows 2000 → All
QA Contact: ian → madhur
->Inline, not Tables.
Assignee: table → block-and-inline
Status: UNCONFIRMED → NEW
Component: Layout: Tables → Layout: Block & Inline
Ever confirmed: true
QA Contact: madhur → ian
Assignee: layout.block-and-inline → nobody
QA Contact: ian → layout.block-and-inline
You need to log in before you can comment on or make changes to this bug.