Open Bug 76545 Opened 24 years ago Updated 5 years ago

paste of table column should maintain column layout

Categories

(Core :: DOM: Editor, enhancement, P5)

enhancement

Tracking

()

People

(Reporter: Brade, Unassigned)

References

Details

(Whiteboard: 6 days)

* create a 3 by 3 table; put a number in each to match telephone pad layout * click in the first cell * choose Table | Select | Column * choose Edit | Copy * create a new composer page * choose Edit | Paste notice that the cells are pasted as a row instead of as a column. This is not a duplicate of bug #41547 (though they will share some infrastructure).
This *is* a duplicate of 41547 or a "wontfix" We are *not* keeping row/columns structure when copying to the clipboard. A user must use the (not implemented yet) "Paste Special > Paste as Columns" to get a column of cells. Right, Joe?
Think of this bug as a FUTURE/RFE where we'd have a proprietary format we put on the clipboard which could help us know if we have rows or columns or whatever. Bug #41547 could be implemented without this bug being fixed and vice versa (so I didn't add any dependencies).
Severity: normal → enhancement
Target Milestone: --- → Future
Who's responsible for the "copy to clipboard" code? That's where the information concerning copied table layout should be addressed. Joe?
Assignee: cmanske → jfrancis
This needs to be addressed sometime sooner than "future". There are known dups of this.
Target Milestone: Future → mozilla1.0
*** Bug 89323 has been marked as a duplicate of this bug. ***
*** Bug 94177 has been marked as a duplicate of this bug. ***
Status: NEW → ASSIGNED
Whiteboard: EDITORBASE; 6 days
Whiteboard: EDITORBASE; 6 days → EDITORBASE-; 6 days
Agree with EDITORBASE-, removing EDITORBASE
Whiteboard: EDITORBASE-; 6 days → 6 days
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
*** Bug 128309 has been marked as a duplicate of this bug. ***
The trunk is the wave of the future!
Target Milestone: mozilla1.0.1 → mozilla1.1beta
The days of having a half dozen milestones out in front of us to divide bugs between seem to be gone, though I dont know why. Lumping everything together as far out as I can. I'll pull back things that I am working on as I go.
Target Milestone: mozilla1.1beta → mozilla1.2beta
don't we have lots of duplicates of this bug?
Keywords: nsbeta1
*** Bug 161731 has been marked as a duplicate of this bug. ***
Keywords: nsbeta1nsbeta1+
I'll try to get to this sometime soon.
Target Milestone: mozilla1.2beta → M1
differentiating bug severity of my most critical bugs vai abuse of milestone field M2: severe M1: very severe and/or fix in hand
Target Milestone: M1 → M2
QA Contact: sujay → editor
Assignee: mozeditor → nobody
Status: ASSIGNED → NEW

Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.

Severity: normal → S4
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.