Closed Bug 91894 Opened 25 years ago Closed 24 years ago

Selecting a message doesn't always select the message on the first attempt

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: Peter, Assigned: sspitzer)

Details

(Keywords: regression)

Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.2+) Gecko/20010722 Selecting a message doesn't always select the message on the first attempt. I think this happens most often when selecting a message in a folder that is different from the one previously selected. Reproduce: - look at a message in one folder - select another folder and select a message there Result: - message is not selected (only after second attempt) Expected Result: - message is selected (and shows contents below).
These are very genereal steps; I've never experienced this.
I think it only happens with local folders (not sure tho) and when I "quickly" select the message (i.e., the messages have just become visible -> ~0.5 sec.) after selecting the folder. It doesn't seem to happen after repeated tries (cache?).
Sorry, keywords won't fix the bug. (Taking away incoherent keywords.)
Keywords: 4xp, mail3, mail4, mozilla0.9.3, ui
Peter Lairo: for me the reported need for double click exists only when selecting something in a text field and trying to set focus to another text field. E.g. you type something in address field and autocomplete displays a proposed address that is selected. Then you need double click to give focus to the subject field. But I never saw something similar during message selection.
Dimi: What you describe should be a separate bug. <OT> Yassu! Actually, you can (finally) TAB out of the autocomplete address once you have selected (by cursor) the address :) <OT\>
worksforme with 090904 mozilla branch build on win2K.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Worksforme sep27 branch and trunk.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.