Closed
Bug 1908
Opened 26 years ago
Closed 25 years ago
Style sheet rendering foobar'ed
Categories
(Core :: Layout, defect, P2)
Tracking
()
VERIFIED
FIXED
M6
People
(Reporter: blizzard, Assigned: rickg)
References
()
Details
This page renders text on top of the the supposed-to-be-right-aligned box. This could be bad html, I'm not sure but it renders well in other browsers.
Looks like a broken table width to me, especially since the remaining of the un-overlapped content is as narrow as it is.
Updated•26 years ago
|
Status: NEW → ASSIGNED
Comment 3•26 years ago
|
||
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Updated•25 years ago
|
Assignee: karnaze → rickg
Status: ASSIGNED → NEW
Comment 4•25 years ago
|
||
In the following extraction (with some substitutions) of the url, there is a nested <table> with a single <tr> which doesn't have a <td> specified. When I added the <td>, the test looks much better. Without the <td> the content model is missing a cell in the row. Also note that even by not having the <td> if you remove the <font> and </font>, the test starts looking better as well. <HTML> <body> <table border="0" width="605" cellspacing="0" cellpadding="0"> <tr> <td bgcolor="#CCFF00" colspan="2" valign="TOP"><hr width="110" height="30"></td></tr> <tr> <td bgcolor="#ffff99"> </td> <td bgcolor="#ffff99"> </td></tr> <tr> <td colspan="2" bgcolor="#FF6600"> <table border="0" cellspacing="0" cellpadding="5"> <tr> <form> <font face="courier" size="1"><td valign="middle" bgcolor="#FF6600"><nobr> <input type="TEXT" name="query" value="" size="20"> </font> <select name="url"></select> <input type="SUBMIT" name="SUBMIT" value="SEARCH"> </td> </form> </tr> </table> </td> </tr> </table> </body> </html> This was done using 4/5 pm WinNT debug.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 6•25 years ago
|
||
Fixed in June 2 Build.
You need to log in
before you can comment on or make changes to this bug.
Description
•