Closed Bug 218753 Opened 22 years ago Closed 20 years ago

Hotkeys are all capiitals in menus, but they are all small when invoked

Categories

(SeaMonkey :: General, defect)

x86
All
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: brainbench, Assigned: henrik)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Hotkeys are always in big capitals, but they only work when they are invoked in small capitals. This is not trivial, say after using VI, and it isn't correct either in terms of precision. Reproducible: Always Steps to Reproduce: 1. type "CTRL-N", as seen in menu 2. nothing happens 3. type "CTRL-n" Actual Results: New windows appeared only when typing "CTRL-n", and nothing happened when "CTRL-N" was invoked, as stated by the menu. Expected Results: Open new window it is like this in the English version
chrome://help/locale/shortcuts.xhtml#using_shortcuts explains the format Mozilla uses in referring to shortcuts, and does explain clearly that letters which appear in shortcut descriptions refer to keyboard buttons--not typed letters. To quote: "To perform a command, press the buttons listed together at the same time. For example, to copy in Windows, press Ctrl and C at the same time. Tip: The plus sign (+) means that you must press two keys surrounding the plus sign at the same time. If there is more then one plus sign (such as Ctrl+Shift+C), it means that all three buttons surrounding the plus sign must be pressed at the same time." Mozilla must use some method to explain keyboard shortcuts. The very widely used system currently employed (referring to the text that is most likely to appear on the keyboard buttons) seems very sufficient to me.
moving to browser product, this is not mozillaTranslator related
Component: MozillaTranslator → Browser-General
Product: Mozilla Localizations → Browser
Version: unspecified → Trunk
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.