Open Bug 82648 Opened 24 years ago Updated 2 years ago

Performance: Attempt to find a menu short-cut when press <alt>+<up arrow> and other non-char keys

Categories

(Core :: XUL, defect)

x86
Windows 2000
defect

Tracking

()

Future

People

(Reporter: tetsuroy, Unassigned)

Details

We should not iterate thru the MenuBar ShortCut for non-char keys.

Here is the steps:
1) run debugger
2) open browser
3) set breakpoint on line 197 nsMenuBarListner.cpp
4) press <alt>+<up arrow>
5) stops at the break point, 
6) check for theChar value.  It's NULL.
7) we go and iterate a short cut to find a match.  <=== not necessary.

---------- //layout/xul/base/src/nsMenuBarListener.cpp [approx. line 197]----
keyEvent->GetCharCode(&theChar);
PRBool active = PR_FALSE;
mMenuBarFrame->ShortcutNavigation(theChar, active);
.....
-------------------------------------------------------------------------
Status: UNCONFIRMED → NEW
Ever confirmed: true
This is event system usage by menus, not the event system itself
Assignee: joki → pinkerton
Component: DOM Events → XP Toolkit/Widgets: Menus
QA Contact: vladimire → jrgm
ok
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Should be as simple as...

keyEvent->GetCharCode(&theChar);
if (theChar) {
  PRBool active = PR_FALSE;
  mMenuBarFrame->ShortcutNavigation(theChar, active);
  .....
}
i'll take this, if it's still relevant
Assignee: pinkerton → dean_tessman
Status: ASSIGNED → NEW
Back to default owner.  Suggested fix is in comment 3.
Assignee: dean_tessman → nobody
QA Contact: jrgmorrison
Component: XP Toolkit/Widgets: Menus → XUL
QA Contact: xptoolkit.widgets
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.