Closed
Bug 14218
Opened 25 years ago
Closed 25 years ago
[Dogfood] Copy/paste HTML from 4.x is broken
Categories
(Core :: DOM: Editor, defect, P3)
Tracking
()
VERIFIED
WONTFIX
M13
People
(Reporter: phil, Assigned: mikepinkerton)
Details
I used to be able to copy text from the editor in 4.x, and paste it into Seamonkey, and have all the HTML preserved. Now, I get only a plain text representation, with links removed, and bulleted lists turned into a run of spaces
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M12
Comment 1•25 years ago
|
||
I'll look at it whenever I get a usable Windows build (today's is crashing on startup). This can't be tested on Linux because we haven't been able to find any Linux apps which paste html. Phil, since you obviously have a working NT build, could you do me a favor? In editor/base/nsHTMLEditor.cpp around line 3167, there's an ifdef DEBUG_akkana to print the flavor the transferable wants to give us. Could you switch the ifdef so you'll see the printf (or just break in the debugger there) and tell me what the flavor string is? This would at least pin down whether it's a clipboard problem or an editor or doc encoder problem.
Reporter | ||
Comment 2•25 years ago
|
||
The flavor is text/plain
Updated•25 years ago
|
Assignee: akkana → pinkerton
Status: ASSIGNED → NEW
Comment 3•25 years ago
|
||
Shouldn't it be text/html? Pinkerton, could whoever owns the windows clipboard now look into this? I haven't had a good success rate with getting working Windows builds.
Assignee | ||
Comment 4•25 years ago
|
||
accepting
Comment 5•25 years ago
|
||
mass-moving all m12 bugs to m13
Updated•25 years ago
|
Summary: Regression: Copy/paste HTML from 4.x is broken → [Dogfood]Regression: Copy/paste HTML from 4.x is broken
Comment 6•25 years ago
|
||
Product marketing would like the ability to cut/paste HTML from within Seamonkey components as a dogfood feature (i.e. Mail and Composer). Would like to bring this to PDT's attention.
Reporter | ||
Comment 7•25 years ago
|
||
Bijal, this bug is between 4.x and Seamonkey. If there's a particular case of copy/paste *within* Seamonkey which doesn't work, you should probably file a separate bug. Personally, I see HTML copy/paste as being hit-or-miss right now.
Unless this is needed for the marketing demo, interaction here between 4.x and5.0 is not dogfood. Putting on PDT- radar
Assignee | ||
Comment 9•25 years ago
|
||
my guess is that this is related to 17599. it surprises me that all this used to work but now it doesn't. Hrm. Well, i'll investigate.
Assignee | ||
Updated•25 years ago
|
Summary: [Dogfood]Regression: Copy/paste HTML from 4.x is broken → [Dogfood] Copy/paste HTML from 4.x is broken
Whiteboard: [PDT-]
Assignee | ||
Comment 10•25 years ago
|
||
Removing "regression" from summary since both rod and I are pretty sure that this never worked and never could have.
Comment 11•25 years ago
|
||
Yes, I will go on record say this NEVER worked. From my intimate understand of our copy/paste code and having a general understand of 4.x copy/paste code... This just never worked.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
Assignee | ||
Comment 12•25 years ago
|
||
After talking to Rod and Kathy, it appears that the format that 4.x uses for passing around HTML is a binary data structure. We do not want to attempt to duplicate that. The editor team explicitly does not want to handle backwards compatibility, especially since you can't even copy from 4.X _Navigator_ to 4.x composer and have it retain the html! Marking WONTFIX, as advised by Kathy.
Comment 13•25 years ago
|
||
verified in 1/13 build.
Comment 14•25 years ago
|
||
This doesn't means that we won't support copy/paste between mozilla and other external apps that support html on Mac and Windows, right? Just that the 4.x binary format is incompatible with these and so that's what we're not supporting? I see html copy still works within our app, so that's not at issue.
Assignee | ||
Comment 15•25 years ago
|
||
Right.
You need to log in
before you can comment on or make changes to this bug.
Description
•