823843 - When an e-mail is autosaved the cursor moves to the position [1st line, 1st character]

Status: RESOLVED DUPLICATE of bug 551568

(Thunderbird :: Message Compose Window, defect)

Description

[Dźmitry]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20100101 Firefox/10.0.11 Iceweasel/10.0.11
Build ID: 20121120224241

Steps to reproduce:

I compose an e-mail using the mail composer window with the auto-save function enabled

Environment details: 
OS: Linux z 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux
DE: xfce 4.8


Actual results:

When a draft version the e-mail I compose is auto-saved the cursor moves to the first line and first character so that the text I type is written in the incorrect place


Expected results:

Either
- the message body should be non-editable while saving
or
- the cursor should not change its position while auto-saving

Comment 1

[Thomas D. (:thomas8)]

Thanks Dzmitry. Pls don't set Priority.
worksforme(wfm) on WinXP/TB17, but reported against Linux.
Can sombody confirm for Linux?

Comment 2

[Dźmitry]

I have just tested more cases. I need to add that when I do not type text when auto-save is triggered then the cursor does not change its position. You need to type text while the e-mail is being saved.

Comment 3

[Dźmitry]

In addition, this bug is not somewhat always re-producible. I usually see this when the e-mail is auto-saved first time. After a couple of auto-saves the cursor holds its position even when I type text while the e-mail is being auto-saved.

Comment 4

[:aceman]

Are able to use a newer TB version?
Since bug 271730 (TB19) the window should be disabled/locked while Saving is in progress. Maybe you could temporarily try that development version to see how it behaves.

Comment 5

[Dźmitry]

Sorry, but I'm not able to do this.

Comment 6

[:aceman]

I couldn't reproduce this on TB20, linux.

Comment 7

[Thomas D. (:thomas8)]

dzimitry, are you working on a laptop with touchpad? Can you switch off the touchpad and see if you still see this bug?

Comment 8

[Thomas D. (:thomas8)]

dzimitry,

account type (Pop or imap)?
composing in html?
any other particulars about those compositions, (large) attachments, inline images etc.?

Comment 9

[Dźmitry]

I use a notebook with a touchpad (enabled, unused) and a mouse (enabled, used). Sorry, but I don't know how to switch off the touchpad in Debain. The only device I use while typing is the keyboard (USB, external). Note that the "mouse" cursor does not move. Talking about 'cursor' I mean the 'caret' within the text area.

The email format: HTML (in the 'plain text' the problem is not reproducible)
Account type: IMAP
Content type: just text - as below. That first <space>o were typed after the cursor changed its position:
 ofj j j jj j jk kkk kk  kk kk kkf
ffffj j jj j jj j j i  ii i i ii i i ii iii ii iii ii ii iii iiii
 ooo oooo ooo oo ooooo oooo ooo o  ooooo o o oo o ooo oo oo o oo
oo o oo o o oo o ooo oo o oo ofofooo oo oo oo ooo
o ooo o ooo ooo ooo oo o oo oo o kfkfkk oo iiddd ii i  i0 00 0 000 o o oo o
o o oo o ooo ooo

Comment 10

[Thomas D. (:thomas8)]

Dźmitry, thanks for providing information on this bug.
Do you still experience this bug on TB version 24?

Our best bet at this time is to consolidate related bug reports and then hope for somebody to fix this, although in the big scheme of things, it might be considered minor (e.g. compared to dataloss bugs).

Comment 11

[Artūrs]

Thomas - I'm still expiriencing this bug on TB 24.6.0 - it's really annoying. And it's been more than four years since this bug surfaced - how comes that it's still present, even considering that TB have been rewritten almost from scratch during this period?

(In reply to Thomas D. from comment #10)
> Dźmitry, thanks for providing information on this bug.
> Do you still experience this bug on TB version 24?
> 
> Our best bet at this time is to consolidate related bug reports and then
> hope for somebody to fix this, although in the big scheme of things, it
> might be considered minor (e.g. compared to dataloss bugs).
> 
> *** This bug has been marked as a duplicate of bug 551568 ***