Closed Bug 12551 Opened 22 years ago Closed 21 years ago
Tracking bug for annoying Copy/Paste formatting behaviors
Background: In 5.0, text selections copied from Seamonkey to other applications will be formatted so that they lack the annoying formatting idiosyncracies of Navigator 4.x copying. (e.g. such as from within a non left-most table cell.) The expected behavior will be "non-annoying" formatting; specifically, under the most common use cases, the output upon pasting text copied from Communicator should be formatted as optimally as is practical.
Item #1: (per discussion with Akkana) When copying text that contains <BR>s, the <BR>s should translate to line breaks in the Clipboard content.
[setting Milestone to M15]
Accepting bug; this will be a placeholder for any annoying/unexpected behavior noticed in unformatted plaintext. One current bug which I need to fix: an extra space gets inserted before items which have inline formatting (like <b>) in the html.
Item #1: If you copy text from a web page whose source contains a word, followed by a space, followed by a line break (not a <BR>; an actual line break), followed by a word, there will be two spaces in between the words. For example, on www.mozilla.org, if you copy the "Codestock is a two day..." paragraph and view it in the Clipboard, you'll see "web content with" (two spaces b/w 'content' & 'with'). The source is: <---> web content with <---> (with a space after the word "content")
Broke the second "Item #1" into bug #13442. Thus, this bug no longer contains any actual bug information, and is now just a set of dependencies for annoying/unexpected behaviors in copying unformatted plaintext.
Changing Component to Output.
Bulk move of all "Output" component bugs to new "DOM to Test Conversion" component. Output will be deleted as a component.
Eli: is it okay if I close this bug? It seemed like a good idea at the time, but I think it's outlived its usefulness and we can track 13401 by itself more easily than through this bug.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
verified in 3/3 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.