Closed Bug 1908 Opened 26 years ago Closed 26 years ago

Style sheet rendering foobar'ed

Categories

(Core :: Layout, defect, P2)

Product:
Core
Component:
Layout
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: blizzard, Assigned: rickg)

References

(
URL
)

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.
Assignee: kipp → buster
Looks like a broken table width to me, especially since the remaining of the un-overlapped content is as narrow as it is.
Status: NEW → ASSIGNED
Assignee: buster → karnaze
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Setting all current Open/Normal to M4.
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Assignee: karnaze → rickg
Status: ASSIGNED → NEW
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">&nbsp;</td> <td bgcolor="#ffff99">&nbsp;</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>&nbsp;<input type="TEXT" name="query" value="" size="20">&nbsp;&nbsp;</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: 26 years ago
Resolution: --- → FIXED
Fixed with update to parsing engine.
Status: RESOLVED → VERIFIED
Fixed in June 2 Build.
You need to log in before you can comment on or make changes to this bug.