Tooltips for buttons should display keyboard shortcuts. For example, Reload Reload current page (Ctrl+R) Stop Stop loading the current page (Esc) Navigator (on "taskbar") Navigator (Ctrl+1) Please move this to a milestone or two before NS6 so that it can be fixed as the keyboard shortcuts themselves stabalize. Note that keyboard shortcuts differ across platforms, but that problem has to be dealt with in menus anyway.

I can't think of another application which does this, and I'm not sure if the usefulness would outweigh the clutter. Also, what do you do for commands which have more than one keyboard shortcut?

Microsoft Word has this as an option (off by default), and it's always the first option I change when I start using Word. On the other hand, a word processor has more buttons, and its buttons aren't generally duplicated on menus (where there's plenty of room for keyboard shortcuts to be listed). Word processors are also generally more keyboard-oriented than browsers. When there's more than one keyboard shortcut, there should be a flamewar in which at least the following are brought up: which shortcut is more intuitive (and thus easier to remember), which has been around longer or is also used by other browsers/programs, and which is easier to hit for both left-handers and right-handers.

Sending to German for comment. cc lake.

For Acessability reasons there will probably be in the near future, skins allowing different shortcuts. If we impliment this here how will this effect those skins. Just as an example, for those who require one stroke grouped comands because of mobility reasons will have the option to use less intuitive commands infavor of those they can physically reach. If implimenting tooltiop shortcuts here hinders the other I would not think it buys much for the cost.

Lake, I hope you're joking. Keyboard shortcuts are part of chrome, and should not be affected by skins, ever. If there are accessibility problems with keyboard shortcuts that cannot be solved by Sticky Keys, then they should be fixed in the chrome -- by (skin-independent) customization, if necessary. To limit disabled users to a choice of a few skins, because they were the only ones with the accessibility-friendly keyboard shortcuts, would be quite discriminatory. Having said that, I fail to see how that would affect the feasibility of this bug one way or the other.

No I was not jokeing, I don't joke about the dissabled. However I did misunderstand a communication with others concerning this. Now I get it when they were talking about making it a preference. (This is still in speculation phase so don't go fileing bugs every one.) And I was not trying to limit them but give then A viable option which they do not currently have. From your info It won't effect skins. And we will handle the other problems else where.

mass-moving UI:Design Feedback bugs to hangas

Chaning the qa contact on these bugs to me. MPT will be moving to the owner of this component shortly. I would like to thank him for all his hard work as he moves roles in mozilla.org...Yada, Yada, Yada...

updating to new owner. sorry for the spam.

An example of a program that does this is Visual Studio. It's one nice way of making keyboard shortcuts easily discoverable.

See also bug 81563, Context menus should include shortcut keys (wontfix).

Will work with UI designers on a plan for this

-> Akkana

Future for now, because we don't have any way to get this information. If xul/xbl key handling gets extended to add this capability (bug 71779), I'll pull this one in.

I think this should be wontfix because it would look lame and not be very useful. If you want to see the keyboard shortcuts, look in the menus.

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

I like this as an idea to help a user get to know how to use their browser more efficiently in a fairly unintrusive manner. In addition to the Mozilla UI it might be nice to also display shortcuts in tooltips for elements with access keys in a webpage. I realise that there is bug 56701 on underlining access keys, but I'm not sure that's a good way of doing it. In common usage the access key often doesn't appear in the text (if there is text, it could be an image link etc etc). A tooltip would be universally usable for this purpose regardless of the content the accesskey applies to. Eg http://www.wrexham.gov.uk/top_navigation/accesskeys.htm

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

The patch displays the shortcuts along with tooltips for Back, Forward,Reload and Stop buttons.

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

This would be a valuable tool for learning the tool tips, there are probably shortcuts I could be using that I just don't know about. Is there a plug in that creates this behavior?

Comment on attachment 183005 [details] [diff] [review] shows shortcuts along with tooltips Hardcoding the shortcut keys in browser.dtd's tooltip entities does not look like a sustainable approach, they should be retrieved dynamically from somewhere and added to the tooltip at runtime --> Patch attachment 183005 [details] [diff] [review] is obsolete. I'd appreciate a confirmation from someone that I am doing the right thing in obsoleting this patch. :)

Akkana Peck (akzilla@...), is it still correct that you are assigned to this bug as per comment #13? If not, please let us know or change "assigned-to" accordingly.

No, I'm definitely not the right assignee for this one.

Is this applicable to Windows OS only? Otherwise, please let me know, Platform and OS should be changed to "ALL".

I'd like to make a comment to this one: Now, that the default policy of Thunderbird has changed to not showing the main menu bar, how many inexperienced users know how to open it again? So an inexperienced user will always use the buttons around or maybe thecontext menu nowadays, not a menu bar he can't see. So I'd really like to see shortcuts in tooltips (and context menus, as mentioned in Bug 81563)