176385 - cannot copy/paste multiple cell contents within table without disturbing structure

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[lloyd]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021016
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021016

There should be a way (if there isn't one already?) of moving a range of cell
contents to a new region of a table.

Cut/paste will nest the selected cells *into* the first target cell.  And,
perhaps worst of all "undo" does not undo this operation.  (Perhaps that should
be filed as a separate bug?)

Reproducible: Always

Steps to Reproduce:
Example 1:  Try rearranging the order of columns in a table.

Example 2:  Try shifting the contents of a range of cells diagonally within a table.

Comment 1

[Syd Logan]

--> charley

Comment 2

[Jani Patokallio]

I can confirm this behavior, and ir remains unfixed in Mozilla 1.3alpha.
Please do something(tm).

Comment 3

[lloyd]

why is this bug still unconfirmed?  it's easy to reproduce:

1 create a table and put some content in the cells

2 highlight a range of cells and copy them

3 highlight another range of cells (of the same size) and paste


expected results: copied cell contents pasted into the highlighted range of cells

actual results:  hard to describe - table structure gets all messed up - cells
pasted inside of other cells, not all data pasted anyway.

it's really broken, and makes it extremely difficult to edit tables.

Comment 4

[mozilla.gv6r]

Please confirm bug.  Occurs on Win 2000 in the Composer shipped with Mozilla 1.4
released build.

Cut-and-paste in a table (within Composer WYSIWYG view) works very strangely.

1: Start composer, and insert a reasonably sized table (5x5 or so shoudld be
sufficient)
In the table, set the cells like this:
A1 B1 C1 D1 E1
A2 B2 C2 D2 E2
A3 B3 C3 D3 E3
A4 B4 C4 D4 E4
A5 B5 C5 D5 E5
2: Select a 2x2 set of cells (perhaps A1, B1, A2, and B2)
3: Copy those to the clipboard.
4: Select 2x2 set of Cells C2,D2,C3,D3 
5: Paste
6: Notice that original cell C2 now contains A1, and orig. cell D2 contains a
nested table containing 3 columns with cells containing B1, A2, and B2 all on
one row.  Original cells C3 and D3 are missing.

Expected behavior:
Orig. cells C2, D2, C3, and D3 should contain contents of original cells A1, B1,
A2, and B2.  No nested table should be generated.

Comment 5

[mozilla.gv6r]

One further comment (sorry, I should have said this before)...

After you paste, the Edit->Undo function will not undo the change properly.  It
partially undoes the paste, possibly deleting the last cell pasted (B2 in my
example), or doesn't do anything (if a nested table gets generated).

And, the nested table isn't always generated, but Composer still gets pasting wrong.

Comment 6

[Robert Kaiser]

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

Comment 7

[Robert Kaiser]

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

Comment 8

[Robert Kaiser]

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

Comment 9

[Robert Kaiser]

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