cursor disappears when saving composed email in an imap account

RESOLVED WORKSFORME

Status

Thunderbird
Message Compose Window
--
trivial
RESOLVED WORKSFORME
12 years ago
10 years ago

People

(Reporter: uwestoehr, Assigned: Scott MacGregor)

Tracking

x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; de; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; de; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2

To reproduce: You need an IMAP account in Thunderbird. Compose a new email with an IMAP account. Write some text in the compose window and save it with Ctrl-S. After a save the cursor disappears. You can now continue to write text in the compose window and also the write position is not lost, only the cursor. The cursor will first be reappear when you click in the compose window with the mouse.
This problem does only occur with accounts that uses IMAP.

Reproducible: Always
(Reporter)

Comment 1

12 years ago
Sorry, for the wrong user-agent. I use Thunderbird Version 1.5.0.2 (20060308). The bug was also in version 1.0 of Thunderbird.

Comment 2

12 years ago
There was just a large amount of work done to improve the rendering of the 
caret (aka "cursor") in bug 287813, but that fix won't be in Thunderbird until version 3.0.  You can try using a nightly trunk build of TB, but the trunk is not stable, likely to have other bugs.
(Reporter)

Comment 3

12 years ago
Even if it won't be fixed before Thunderbird 3.0 the bug status should be set to confirmed so that it isn't lost.
Version: unspecified → 1.5
QA Contact: message-compose

Comment 4

10 years ago
WFM version 3.0a2pre (2008061103).  fails 2.0 as described.
uwestoehr, status of WFM doesn't mean problem doesn't exist in 2.0.
but bug of this severity won't ever get fixed in 2.0, so closing.
Severity: normal → trivial
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.