If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

accesskey attribute not working in context menus

VERIFIED FIXED in M15

Status

()

Core
XUL
P4
normal
VERIFIED FIXED
18 years ago
18 years ago

People

(Reporter: Bill Law, Assigned: David Hyatt)

Tracking

Trunk
x86
Windows NT
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
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.

Updated

18 years ago
Assignee: trudelle → saari
Priority: P3 → P4
Target Milestone: M14

Comment 1

18 years ago
reassigning to saari as p4 for m14

Updated

18 years ago
Blocks: 6290

Comment 2

18 years ago
Eh... accesskeys shouldn't be defined in context menus... they apply to menu
titles, and context menus don't have menu titles
(Reporter)

Comment 3

18 years ago
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.

Comment 4

18 years ago
mass moving m14 bugs to m15

Updated

18 years ago
QA Contact: claudius → elig

Comment 5

18 years ago
[Contextual menu bug --- QA Assigning to self.]
QA Contact: elig → sairuh
spam: QA reassigning to me.
Assignee: saari → pinkerton
taking popup/menu bugs.
Depends on: 14574
bulk accepting xpmenu/popup bugs. sigh.
Status: NEW → ASSIGNED
(Assignee)

Comment 9

18 years ago
Taking back.
Assignee: pinkerton → hyatt
Status: ASSIGNED → NEW
(Assignee)

Comment 10

18 years ago
Fixed.
Status: NEW → RESOLVED
Last Resolved: 18 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.