User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/85.7 (KHTML, like Gecko) Safari/85.5 Build Identifier: Mozilla Thunderbird 0.3 (20031013) Any entry of the letter 'c' in the message search text field ("Subject or Sender contains:") triggers the Cmd-C menu item, "Message -> Mark -> As Read By Date..." instead of allowing the letter 'c' to appear in the message search text field. Verified this on MacOS X 10.2.8 running Mozilla Thunderbird 0.3 (20031013). Reproducible: Always Steps to Reproduce: 1. start Mozilla Thunderbird 0.3 (20031013) on MacOS X 10.2.8 2. try to type the word "ostrich" into the message search text field 3. upon entering "ostri" and then c, rather than add the letter 'c' to the search text field, the command "Message -> Mark -> As Read By Date..." panel pops up Actual Results: "Message -> Mark -> As Read By Date..." menu item is invoked Expected Results: the letter 'c' is added to the message search text entry field where do I get MacsBug? Sorry, I didn't find anything but references to commands to use once you have MacsBug on www.mozilla.org

I've run into this on Panther 10.3.2, using Thunderbird 0.5, and it's supremely annoying. Is there any way to re-bind the menu items to have a modifier key associated with them instead, at least for the OS X build? The idea of a menu item being triggered without a modifier is very un-Mac-like.

(In reply to comment #1) > The idea of a menu > item being triggered without a modifier is very un-Mac-like. Very true. Menu commands on OS X should always require the command key. The problem is finding unique command key equivalents for these commands. For example, Cmd-C is already in use as "Copy." "Mark All Read" is Cmd-Shift-C. So does "Mark as Read By Date" become Cmd-Shift-Option-C, or something else altogether? FWIW, in the 0.7 branch build (20040611), typing "ostrich" dies even earlier than the 'c' because of "Go -> Next Unread Thread".

WFM with 10.3.4 & Thunderbird 0.7. reporter, please re-open this bug if you can still reproduce the issue with a nightly build.

other users have reported this issue

*** This bug has been marked as a duplicate of 199019 ***