Closed Bug 204965 Opened 23 years ago Closed 21 years ago

"Select Thread" keyboard shortcut Ctrl+Shift+A no longer works

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 186789

People

(Reporter: calum.mackay, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030508 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030508 When viewing mail in threaded mode, Edit-Select-Thread selects all the mail in the current thread. This menu option has a keyboard shortcut - mentioned on the menu itself - of Ctrl+Shift+A. The shortcut no longer has any effect (although the menu still works correctly). Reproducible: Always Steps to Reproduce: 1.Select a message in a thread containing more than just that one message 2.Ctrl+Shift+A 3. Actual Results: Nothing Expected Results: All messages in the thread should be selected Looking back over my builds, this appears to have stopped working in the 6 hours period between my cvs builds: 2003043005 2003043011 where the checkout hour times are in GMT.
Can't reproduce this on Solaris with this cvs: $ ./thunderbird --version Mozilla 1.5a, Copyright (c) 2003 mozilla.org, build 2003063016 My build/cvs checkout appears to be newer than Calum's.
dupe of bug #186789 ? (are you using gtk2?)
Blocks: 236849
WFM under Win2K with Moz1.7 and TB 0.8. Calum Mackay, is this bug still a problem for you? If so, do you have any response to comment 2? If not, please resolve this bug either as a dupe of that one, or as WorksForMe.
Yes, sorry, this one was a dupe of 186789, and I should have closed as such a long time ago. Sadly, I am still seeing the problem, since the bug hasn't been fixed on Thunderbird, but that's another story. *** This bug has been marked as a duplicate of 186789 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
No longer blocks: 236849
You need to log in before you can comment on or make changes to this bug.