signature: wrong copying to clipboard from non-f=f letter

RESOLVED INCOMPLETE

Status

RESOLVED INCOMPLETE
13 years ago
9 years ago

People

(Reporter: arkady.belousov, Unassigned)

Tracking

({qawanted})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: closeme 2009-10-30)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; ru) Opera 8.54
Build Identifier: http://mozilla-chi.osuosl.org/pub/mozilla.org/thunderbird/releases/1.5.0.4/win32/ru/Thunderbird%20Setup%201.5.0.4.exe

If there is letter, which contains signature (text after line with "-- "), then copying signature (clipboard) gives different results depending if there is or no "format=flowed" in Content-Type: field: with f=f signature copied fine, without f=f all line-breaks and leading spaces are replaced by one space (ie.signature text converted into one line).

PS: I mean multiline signature with leading spaces. I not test signatures with other properties.

Reproducible: Always
(Reporter)

Comment 1

13 years ago
Addition: in f=f mode, non-f=f aware mailer shows signature with extra space in each line.

Comment 2

12 years ago
(In reply to comment #1)
> Addition: in f=f mode, non-f=f aware mailer shows signature with extra space
> in each line.

At the end of the line, or at the beginning?

Which mail client is generating the f=f messages that are causing the problem?
Do these f=f messages appear in the message without line breaks, or is the problem only when copying to the clipboard?
(Reporter)

Comment 3

12 years ago
> At the end of the line, or at the beginning?

     Beginning. I not check trailing spaces and doubt they appear, whereas leading space is related to f=f handling (as I understand).

> Which mail client is generating the f=f messages that are causing the problem?

     Thunderbird, of course. In my primary, non-f=f aware mailer (which shows message "as is", without extra handling), shows, that letters, which I send from TB, contains extra leading space in signature.

> Do these f=f messages appear in the message without line breaks, or is the
> problem only when copying to the clipboard?

     Only _copying_ through clipborad in TB breaks signature, showing is fine.
QA Contact: front-end
Assignee: mscott → nobody
Reporter, does this issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported 2.0.0.x is 2.0.0.16)
Whiteboard: closeme 2008-09-25
(Reporter)

Comment 5

10 years ago
Yes, it still occur. Example of letter, currently in my inbox (copied directly from TB' "Inbox." file, with all extra trailing spaces):

|From - Fri Sep 12 16:23:08 2008
[...]
|X-Mozilla-Keys:                                                                                 
|Received: (qmail 41832 invoked from network); 12 Sep 2008 16:23:49 +0400
[...]
|User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
|MIME-Version: 1.0
|To: ...
|Subject: test
|Content-Type: text/plain; charset=KOI8-R
|Content-Transfer-Encoding: 8bit
|
|test
|-- 
|                Best regards! Sincerely yours, Хемуль Советикус.
|       Утомлённый чаем любитель сладкого, в девичестве Бильбо Ленивчатый.
|
|

When I open this letter in TB, select all text (^A), copy to clipboard (^Ins), then I get next:

|test
|-- Best regards! Sincerely yours, Хемуль Советикус. Утомлённый чаем любитель сладкого, в девичестве Бильбо Ленивчатый.
Keywords: qawanted
Whiteboard: closeme 2008-09-25
WFM here with 

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5pre) Gecko/20091010 Lightning/1.0pre Shredder/3.0pre ID:20091010032408

and latest enigmail 0.97a (20091011-0601).

Could you try to see if it still happens with
http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-1.9.1/ ?
Whiteboard: closeme 2009-10-30
RESO INCO due to lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.