Closed Bug 682376 Opened 13 years ago Closed 13 years ago

autosave moves the cursor when replying to a message

Categories

(Thunderbird :: General, defect)

6 Branch
x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 551568

People

(Reporter: jorgevismara, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.861.0 Safari/535.2 Steps to reproduce: reply to a message I received. Actual results: when replying to a message, when I'm writing in the reply window, suddenly the cursor moves by itself to the very beginning of the message window/text area. it took me some time to figured it out... it happens when the AutoSave is triggered. Expected results: the cursor, the position in the text where I'm writing, should stay put in the same place.
Do you have extension installed ?
Good question... I have 3 extensions: Correct Identity, FlashGot and Portuguese orthographic corrector. I'll disable all and see what happens... then I'll re-enable one by one... keep you posted. thanks
(In reply to jorgevismara from comment #2) > Good question... > I have 3 extensions: Correct Identity, FlashGot and Portuguese orthographic > corrector. > I'll disable all and see what happens... then I'll re-enable one by one... > keep you posted. > thanks Ping ?
sorry for the delay... all my tests didn't show any interference from the extensions... the problem persists... thanks,
Hum I don't see that and I run without extensions too. Is your draft folder local or on imap ? At what frequency do you have your autosave set to ?
I see this also on 4 computers with gmail and other IMAP mail accounts. All are on Windows 7. Autosave is turned on for every 1 minute. It seems it hapends only after the first autosave.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Mac OS X → All
BTW I'm now on Earlybird 13a2. And it just happened to me.
This is a dup of 551568.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.