Closed
Bug 58807
Opened 25 years ago
Closed 25 years ago
Copy/paste in tables includes cell
Categories
(Core :: DOM: Editor, defect, P3)
Core
DOM: Editor
Tracking
()
M18
People
(Reporter: trudelle, Assigned: rubydoo123)
Details
Using this morning's MN6 candidate build on Win98.
Edit an HTML document containing a table.
Type some text into a cell.
Select some of the text.
Focus in another cell
Paste.
Expected: text is pasted.
Actual: New, nested cell is pasted, with the text inside it.
| Assignee | ||
Comment 1•25 years ago
|
||
yes, if you select all of the content, then the content and the element gets
copied. That is by design, this will be readdressed in the go round, allowing
for a choice -- just the text or the text and its container(s).
*** This bug has been marked as a duplicate of 46459 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
| Reporter | ||
Comment 3•25 years ago
|
||
reopening. This is clearly a defect,whether it is in the design or
implementation. It is not the same as offering new formatted/unformatted
options for copy/paste. I understand the concept, and know that it is used for
selecting e.g., all of a list item in popular products, although it should
really provide a way of selecting the bullet/cell/whatever to indicate that. I
have never once wanted to nest table cells, although I frequently copy their
contents around, so including the enclosing cell by default on copy/paste of the
contents makes Composer of no use to me for table editing. cc'ing some UI folks.
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
| Assignee | ||
Comment 4•25 years ago
|
||
the issue here is that we are looking at container objects, the td, tr and table
are container objects just like li and ul or ol. Allowing for a choice in future
release provide an option for the end user, however, at the present the current
implementaion will be used.
Remarking as a dup.
*** This bug has been marked as a duplicate of 46459 ***
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → DUPLICATE
| Reporter | ||
Comment 6•25 years ago
|
||
You may be looking at containers, but the person using the editor is just
selecting text. Please reconsider this from a usability perspective.
| Reporter | ||
Comment 7•25 years ago
|
||
I really don't want to be a PITA, but I'm reopening this again. I just realized
it is also the cause of some problems that have been vexing me while editing my
progress reports. When I copy text from bug listings and paste into a mail
message, an invisible table gets pasted in with it. If I then select it all and
delete, the table remains, so the editor is not even being consistent about
which editing operations include the selection's container. Pasting visible
containers is one thing, but when they are not shown, it just appears defective.
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
Peter,
Beth is not marking your bug INVALID or WORKSFORME.
I believe she is marking this bug a DUPLICATE. Which means
that this is a valid bug but is a duplicate of a bug that
is already filed.
Comment 10•25 years ago
|
||
rats! bugzilla lost my comments :-(
I think Peter is right; I don't think this is a duplicate of bug #46459. For
me, the behavior Peter is describing would be fixed for bug #57292.
btw, a workaround (if I remember correctly) is to select all but the first
character (or the last character) in the cell and you won't get the <td>.
*** This bug has been marked as a duplicate of 57292 ***
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
OS: Windows 98 → All
Hardware: PC → All
Resolution: --- → DUPLICATE
Target Milestone: --- → M18
Comment 12•23 years ago
|
||
I don't think this bug is a dupe of bug 57292. That bug is marked fixed, but the
behavior Peter describes still exists. Using a recent commercial build from
20020717 I still see the orginal behavior Peter describes in this bug.
Charley - I remember you mentioning that this issue still exists - can you
comment? If you agree this is not a dupe, I will re-open and nominate for buffy.
You need to log in
before you can comment on or make changes to this bug.
Description
•