Empty tables screws up if done with content

RESOLVED EXPIRED

Status

SeaMonkey
Composer
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: Peter Snyder, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
If I create a table, select the contents of all the cells (or the cells
themselves), and hit delete, the table is emptyed as expected and I can contine
writting.  However, if I immediatle start writting once I have the cells
highlighted, insteand of having the same results as above, the table is screwed
up.  As long as I don't move the cursor out of the table, I can still edit the
first row, but not the others no matter what I do.  The other rows also appear
very small (maybe a 1/3 of expected height).  However, if I save the page with
the screwed up table, exit, and reopen it, the table is fine.

Comment 1

16 years ago
--> cmanske
Assignee: syd → cmanske

Comment 2

15 years ago
I'm confirming this. I can reproduce it with build ID 20030531 on mandrake 9.0.
It can be reproduced as follows:

1) Open composer. Select Insert->Table to create a table.
2) Put the mouse in the top left cell and drag to highlight all cells.
3) Type something, e.g. "foo". It should appear in the top left cell.
Simultaneously, the second and later rows will shrink to a minimum height.
4) Hit down-arrow. The cursor should disappear.
5) Type something. It shouldn't appear anywhere. Hit return a few times.
Depending on what you type, some of the shrunken rows may actually disappear.
6) Switch to the HTML Source view. All the stuff you typed in step five is
inserted between the <tr> and the first <td> for the second row.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 3

15 years ago
Steps 4, 5 and 6 in comment 2 are covered in newer bugs.
The original bug here is a probably caused by lack of moz-br in each cell.
Product: Browser → Seamonkey
Assignee: cmanske → nobody
QA Contact: sujay → composer

Comment 4

9 years ago
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

Comment 5

8 years ago
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
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.