194147 - Selecting "Mark As" causes Quick Search not to work on "m" and "r"

Status: RESOLVED FIXED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Ninoschka Baca]

Trunk build 2003-02-19: Mac 10.2

Overview: You can get into a state where a Quick Search using the letters "m" or
"r" won't work and don't even appear in the Quick Search text box. Instead the
Message menu flashes.

Steps to reproduce:
1. Select a message in the thread pane
2. Select Message|Mark|As Read
3. Type "m" (or "r") in the Quick Search text box

Actual Results: The Message menu flashes and the text you just entered does not
appear in the Quick Search text box therefore you cannot search on items that
include an "m" or an "r".

In Step 2 you can actually choose any item within the Message|Mark and the same
problem will occur (i.e. Thread as Read, All Read, Flag etc...).

Interesting that the letters that are effected also appear in the Message menu
and are the only ones that have accelerators that require a shift (looks lilke
an up arrow)
- Message|New Message has Shift+Ctrl+M 
- Message|Reply to All has Shift+Ctrl+R 

Workaround: Select the Message menu, now "m" and "r" will work.

Expected Results: Quick Search on any letter should perform as expected.
Selecting a menu item should not disable this function.

Comment 1

[Ninoschka Baca]

Marking nsbeta1.

But I just checked and it was also a problem in Netscape 7.01.

Comment 2

[Samir Gehani]

Mail triage team: nsbeta1-

Comment 3

[sairuh (rarely reading bugmail)]

see also bug 195830, where something similar happens with ' and / (for find as
you type) after you view the Edit menu.

i'd say both this and 195830 are blocked by 195979.

Comment 4

[Simon Fraser [no longer active]]

This problem happens because 'M' and 'R' are used as unmodified menu shortcuts
in the Message->Mark submenu. The menus on Mac always get first crack at events.

Comment 5

[Samir Gehani]

Mail triage team: nsbeta1-

Comment 6

[Kathleen :Brade]

This an incredibly frustrating bug and really should be addressed.

Can we at least release note a workaround for Mac users?

Comment 7

[(not reading, please use [e-mail] instead)]

should we do the same thing as aaronl did for bug #195830?

see http://bugzilla.mozilla.org/attachment.cgi?id=116833&action=view

or should we wait for bug #195979 to be fixed?

Comment 8

[H'ik]

I can confirm this with Thunderbird 1.0 Release NL and EN-US.

Typing 'k' in the search box issues 'ignore thread' command. The same happens
with all one key commands.

(Workaround: always use command key modifier. That would also make TB more Aqua
HIG compliant.)

Seems to be very similar to Bug #199019

(please set the severity to major or critical, as this bug really disables the
search box)

Comment 9

[Stefan [:stefanh]]

Attachment: Don't display single commandkeys in mac menuitems

I hate this, but i suppose this is the only way of fixing the issue right now. Just remove any single key from its menuitem. The keys will still work, but you won't see them in the menu. mcscott did this for Thunderbird a while ago.

Comment 10

[[e-mail]]

Comment on attachment 201172 [details] [diff] [review]
Don't display single commandkeys in mac menuitems

Fine, except you missed a bunch of keys; firstly, all six label keys (0-5) and secondly, three captial letters - not Junk, not Scam, show Remote content.

Comment 11

[Stefan [:stefanh]]

(In reply to comment #10)
> (From update of attachment 201172 [details] [diff] [review] [edit])
> Fine, except you missed a bunch of keys; firstly, all six label keys (0-5)

We don't need to remove  those. Typing those numbers in the search box doesn't trigger the bug.

> and
> secondly, three captial letters - not Junk, not Scam, show Remote content.
>

To trigger the bug with those ones the user needs to enter both "Shift" and the relevant key (j, r, p) in the search box. I thought that was a rare case.

 

Comment 12

[Stefan [:stefanh]]

Comment on attachment 201172 [details] [diff] [review]
Don't display single commandkeys in mac menuitems

(In reply to comment #11)
> (In reply to comment #10)
> > (From update of attachment 201172 [details] [diff] [review] [edit] [edit])
> > Fine, except you missed a bunch of keys; firstly, all six label keys (0-5)
> 
> We don't need to remove  those. Typing those numbers in the search box doesn't
> trigger the bug.
We don't even show the keys on mac ;)

Comment 13

[[e-mail]]

Comment on attachment 201172 [details] [diff] [review]
Don't display single commandkeys in mac menuitems

D'oh, I was confusing accesskeys with accelerators :-[
I'm not convinced about the upper case keys though.

Comment 14

[Stefan [:stefanh]]

Attachment: Remove Shift+key combos in Mark submenu as well

New version that also removes Shift+key in the "Mark" submenu on Mac (per irc discussion with Neil)

Comment 15

[[e-mail]]

Comment on attachment 203018 [details] [diff] [review]
Remove Shift+key combos in Mark submenu as well

Nit: 8-space indentation is probably wrong for the win version. And if you're going to fix the VK_DELETE indentation, please fix it in the unix version too.

Comment 16

[Stefan [:stefanh]]

Attachment: Updated version, carrying over flags (checked in on trunk/branch)

Updated version: Fixed indentation in win file (also added one empty line under the delete key section) and VK_DELETE key indentation in unix file. Carrying over flags and asking approval 1.8rc2 for a seamonkey-only change.

Comment 17

[Stefan [:stefanh]]

Comment on attachment 203114 [details] [diff] [review]
Updated version, carrying over flags (checked in on trunk/branch)

Low risk, SeaMonkey only...

Comment 18

[Stefan [:stefanh]]

Comment on attachment 203114 [details] [diff] [review]
Updated version, carrying over flags (checked in on trunk/branch)

Checked in on trunk, waiting for branch approval.

Comment 19

[Stefan [:stefanh]]

Comment on attachment 203114 [details] [diff] [review]
Updated version, carrying over flags (checked in on trunk/branch)

This works around a long-time standing mac issue, has baked on trunk for a  while...

Comment 20

[Ian Neal]

Comment on attachment 203114 [details] [diff] [review]
Updated version, carrying over flags (checked in on trunk/branch)

a=me, one more needed...

Comment 21

[Chris Thomas (CTho) [formerly [e-mail] [e-mail]]]

I checked the patch in on branch.  Since you didn't mark the bug as fixed, I'm not setting fixed1.8 - you can do that if it is in fact fixed.

Comment 22

[Stefan [:stefanh]]

I'm going to mark this as fixed. The root problem is not fixed, but Search works as expected now. Once bug 195979 is fixed, we can put the keys back.