Closed Bug 150403 Opened 22 years ago Closed 14 years ago

Editor preview does not render 1-pixel -high table rows correctly

Categories

(SeaMonkey :: Composer, defect)

Product:
SeaMonkey
Component:
Composer
Platform:
x86
Windows NT
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
RESOLVED EXPIRED

People

(Reporter: christophe.thalet, Unassigned)

References

Details

for 1-pixel-high table rows, the HTML editors "preview" window does *NOT* display
the same visual appearance as the usual browser window: the table rows appear
1-text-line-high instead :-(
problem identified:

the HTML editor component adds a <br> in the <td></td> cell automagically
(but it should not!). additionally, a <br> is inserted after the </table>
tag. here is an example code, correctly displayed in browser but
differently in previewer of html editor 

<html><body bgcolor=#ffffff text=#000000>

<table border=1 cellpadding=0 cellspacing=0 width="100%">

<tr><td>The next table row should be exactly 1 pixel high.<br>
        Mozilla 1.0 Browser component renders it OK,<br>
		but its HTML Editor component renders it 1 line high instead in preview
mode.</td></tr>

<tr height="1" bgcolor="#aa0000"><td></td></tr>

<tr><td> The row above this row should be a 1 pixel high red line. </td></tr>

</table>

</body></html>
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
*** Bug 154080 has been marked as a duplicate of this bug. ***
This behavior is OK if there is text in the cell. For empty cells, though, we
should not put in the <br>s.
*** Bug 160953 has been marked as a duplicate of this bug. ***
*** Bug 160950 has been marked as a duplicate of this bug. ***
reassign to new placeholder
Assignee: syd → composer
Status: ASSIGNED → NEW
Product: Browser → Seamonkey
Assignee: composer → nobody
QA Contact: sujay → composer
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.