4.x had them, 6.x should have them too.

*** Bug 64257 has been marked as a duplicate of this bug. ***

I see that 4.x has them on Linux but not Windows: - Expand + - Expand All * - Collapse - - Collapse All /

None of those are i18n-safe. Mac OS standard for any twisty item is to expand it with Command+Right, and collapse it with Command+Left. In an isolated environment such as a XUL tree, just Right and Left by themselves could work too. Expanding/collapsing all could be achieved by selecting all (Ctrl+A) and using the same key combos.

That's fine, we'll do this per platform and follow conventions. [win] I expect +-* to work, i didn't know about / [and i haven't tried it].

*** Bug 85507 has been marked as a duplicate of this bug. ***

*** Bug 74216 has been marked as a duplicate of this bug. ***

Note: in bug 74216 there was a patch (attachment 29338 [details] [diff] [review]) checked in on 2001-04-05 20:27 that was supposed to add expand/collaps all (but not expand/collas this thread), but accroding to comment #9 on bug 74216 "expand all" was not working properly on RedHat Linux 6.2 (but was working properly on other platforms). OTOH, "expand all" works fine for me on RedHat Linux 7.2 using BuildID 2001111600 (0.9.6 branch), so I believe that only - Expand ("+") - Collaps ("-") were left unimplemented.

ssu, you've got a bunch of similar bugs - wanna take this too?

sure

bug 135483 is a dupe of this one

aaronl wants to use / for type ahead find. both jen and I are ok with him taking /. but we should settle on keys for these four actions. we can look and see if OE or other mail clients have short cuts, and use the same.

cvs build from sunday afternoon (windows) - Expand <right> - Expand All * - Collapse <left> - Collapse All / imo the message as summarized WFM. afaik, : is available, either for collapse all, or for typeahead.

Current behaviour is: - Expand <right> if on first message of thread, none if not - Expand All * - Collapse <left> if on first message of thread, none if not - Collapse All \

There's no way to expand/collapse "the current thread" when the focus is on the message view pane. That's where my focus is most of the time. I can navigate back and forth between messages using f, b, n, p, ...

BTW, at the moment [Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040121], none of /*-+ on the keypad work, /+- on the normal keyboard do NOT work, * on the normal keyboard works, View|Thread|{Expand,Collapse} All Threads work. If this matters my keyboard is jp106, but I guess mozilla uses the translated keycodes form X11, right? (and they obviously are OK, as I can type them above). For both "*", xev gives: keycode 48 (keysym 0x2a, asterisk), XLookupString gives 1 bytes: "*" keycode 63 (keysym 0xffaa, KP_Multiply), XLookupString gives 1 bytes: "*" If there is difference between asterisk and KP_Multiply, shouldn't they both be mapped for the same command?

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420