Leading spaces in selection not exported to clipboard upon copy

RESOLVED FIXED in mozilla14

Status

()

Core
Serializers
RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: hsivonen, Assigned: hsivonen)

Tracking

Trunk
mozilla14
Points:
---
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

6 years ago
Steps to reproduce:
 1) On any Web page, locate a word that has spaces before and after.
 2) Select the space before, the word and the space after.
 3) Press ctrl-c (cmd-c on Mac)
 4) Switch to a plain text editor app (e.g. gedit on Linux; don't switch to a word processor that support styling)
 5) Type two letters (e.g. "AB") in the text editor.
 6) Move the caret between the two letters.
 7) Press ctrl-v (cmd-v on Mac)

Actual results:
The word and the trailing space are pasted. The leading space is not pasted.

Expected results:
Expected all the text in the original selection--including the leading space--to be pasted.
(Assignee)

Updated

6 years ago
Assignee: nobody → hsivonen
Status: NEW → ASSIGNED
(Assignee)

Comment 1

6 years ago
Created attachment 609649 [details] [diff] [review]
Get rid of the quirk
(Assignee)

Comment 2

6 years ago
Note that bug 564737 was about mailnews message conversions and the effect on clipboard export was just collateral damage. The duplicates of bug 564737 are about mailnews message conversion, too.
(Assignee)

Updated

6 years ago
Attachment #609649 - Flags: review?(bugs)

Comment 3

6 years ago
Comment on attachment 609649 [details] [diff] [review]
Get rid of the quirk

Ok, let's try this then.
Attachment #609649 - Flags: review?(bugs) → review+
(Assignee)

Comment 4

5 years ago
Thanks.
https://hg.mozilla.org/integration/mozilla-inbound/rev/7857c5bff017
Flags: in-testsuite+
Target Milestone: --- → mozilla14
https://hg.mozilla.org/mozilla-central/rev/7857c5bff017
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED

Updated

5 years ago
Duplicate of this bug: 762961
You need to log in before you can comment on or make changes to this bug.