Closed Bug 14107 Opened 25 years ago Closed 25 years ago

accesskey attribute not working in context menus

Categories

(Core :: XUL, defect, P4)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: law, Assigned: hyatt)

References

Details

I've specified accesskey= for the menu items in the browser context menu
(defined as <popup id="context"> in navigator.xul; you can test it by
right-mouse clicking in the [Context menu proxy] area of the status bar).  The
access keys aren't displayed at all in the context menu.
Assignee: trudelle → saari
Priority: P3 → P4
Target Milestone: M14
reassigning to saari as p4 for m14
Blocks: 6290
Eh... accesskeys shouldn't be defined in context menus... they apply to menu
titles, and context menus don't have menu titles
What's a menu title?

accesskey is an attribute on a <menuitem>.  <menuitem>s can be contained in a
context menu.  One might like them to work for context menus for the same reason
as for regular menus.

Context menus in Communicator 4.x have "access keys" and I just figured I'd try
to do likewise.
mass moving m14 bugs to m15
QA Contact: claudius → elig
[Contextual menu bug --- QA Assigning to self.]
QA Contact: elig → sairuh
spam: QA reassigning to me.
Assignee: saari → pinkerton
taking popup/menu bugs.
bulk accepting xpmenu/popup bugs. sigh.
Status: NEW → ASSIGNED
Taking back.
Assignee: pinkerton → hyatt
Status: ASSIGNED → NEW
Fixed.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
verif on winNT using opt comm bits 2000022408.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.