Closed
Bug 431684
Opened 16 years ago
Closed 16 years ago
Have navigator/tabbrowser "close" menu items have separate accesskeys
Categories
(SeaMonkey :: UI Design, defect)
SeaMonkey
UI Design
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kairo, Assigned: kairo)
References
Details
Attachments
(1 file)
3.52 KB,
patch
|
neil
:
review+
neil
:
superreview+
|
Details | Diff | Splinter Review |
updateCloseItems() in navigator.js updates the File > Close menu item label with different texts for tabbed and untabbed windows, depending on tabbrowser status. For L10n purposes, we should pair setting this label with also setting the accesskey, because we can't guarantee that the global "close" accesskey from platformCommunicatorOverlay fits with both navigator.properties labels in all languages, and even less for localizers to know that an accesskey from there applies to the strings here. To play nice with L10n tools (pairing labels with accesskeys), it might be good to change the ID for the labels to end in .label at the same time.
Assignee | ||
Updated•16 years ago
|
Summary: Have navitgtor/tabbrowser "close" menu items have separate accesskeys → Have navigator/tabbrowser "close" menu items have separate accesskeys
Assignee | ||
Comment 1•16 years ago
|
||
Here's a patch to pair labels with accesskeys as described in comment #0, using the same accesskey for en-US as currently defined in platformCommunicatorOverlay (which continues to be used with the string from there in non-browser windows).
Attachment #318809 -
Flags: superreview?(neil)
Attachment #318809 -
Flags: review?(neil)
Updated•16 years ago
|
Attachment #318809 -
Flags: superreview?(neil)
Attachment #318809 -
Flags: superreview+
Attachment #318809 -
Flags: review?(neil)
Attachment #318809 -
Flags: review+
Assignee | ||
Comment 2•16 years ago
|
||
Checked in, thanks.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•