14574 - [XBL] Regression: Can't navigate in menus with arrow keys

Status: VERIFIED FIXED

(Core :: XUL, defect, P4)

Description

[cpratt]

Build ID: 1999092208
Platform: Windows NT

To reproduce:
- Launch apprunner
- Wait for the default page to load
- Click into the Location: control
- Press Alt-F to drop down the File menu
- Press the cursor keys to navigate through the menus

Result: Nothing changes in the menu! Instead, pressing the left and right cursor
keys will move the caret around in the Location: control.

Expected result: When a menu is dropped down, cursor keypresses should navigate
in menus and not in the text input widget which previously had focus.

Comment 1

[Antti Näyhä]

Verifying the bug report as valid & definitive.

Comment 2

[joki (gone)]

Hyatt is menu man.  Although they do respond to arrow keys in general this
particular case seems not to work.  Sending to trudelle for assignment.

Comment 3

[Peter Trudelle]

keystrokes may be going to the editor in this case.  reassigning to saari as p4
for m12.

BTW, this is far from 'major' severity, which means 'major loss of function'.
The menus aren't a function, and this bug represents only a trivial
inconvenience in their use.

Comment 4

[cpratt]

Changing severity in accordance with trudelle's comments.

Comment 5

[saari (gone)]

Try it again, I bet it works now (doing a windows build right now)

Comment 6

[cpratt]

Using the 1999092408 build on NT, the problem is still very much there as
described.

Comment 7

[Peter Trudelle]

mass-moving all m12 bugs to m13

Comment 8

[sairuh (rarely reading bugmail)]

with 1999121509 on winNT i can use the arrow keys to move around the menu
items. *however*, when i use the up/down arrow keys, the content in the browser
window also scrolls up and down(!). anyone else see that?

reassigned QA contact to me & updated component.

Comment 9

[Kathleen :Brade]

Changing summary from "cursor" to "arrow"

Comment 10

[Antti Näyhä]

Update on 2000010908 build (WinNT4 SP6):

- I can only move between the first and the last item on the menu;
  pressing 'up' arrow at 'New Navigator Window' takes me to 'Quit',
  and pressing the 'down' arrow takes me back again.  This is, of course,
  correct - but it's not possible to choose any other menu items using arrow
  keys.

- Similarly, pressing 'left' arrow at the file menu takes me to the last menu
  on the right ('QA') and pressing 'right' arrow there takes me back.  Again,
  it's impossible to navigate to any other menu than 'File' and 'QA' using the
  arrow keys.

- 'Up' and 'down' arrows also scroll the page up and down as described by
  sairuh.

Comment 11

[saari (gone)]

David, I'm tossing you this for balance and because you can probably fix it
faster than I can

Comment 12

[Mike Pinkerton (not reading bugmail)]

do you guys want to keep this one or should i take it?

Comment 13

[David Hyatt]

This will automatically fix itself once XBL gets further along.  It's not
actually a bug in menus.

Comment 14

[sairuh (rarely reading bugmail)]

[thanks to pinkerton for the clarification on this.]

i've updated the summary, since i remember it working on older builds...

Comment 15

[Mike Pinkerton (not reading bugmail)]

*** Bug 12219 has been marked as a duplicate of this bug. ***

Comment 16

[leger]

BULK MOVE: Changing component from XP Menus to XP Toolkit/Widgets: Menus.  XP 
Menus component will be deleted.

Comment 17

[Peter Trudelle]

putting on beta1 radar

Comment 18

[David Hyatt]

This was caused by pink's interface map changes to nsMenuFrame and nsBoxFrame, 
etc. etc.  Reassigning to him for triage.

Comment 19

[Mike Pinkerton (not reading bugmail)]

fix in hand, waiting for tree to open. this was a stupid regression. apologies.

Comment 20

[Mike Pinkerton (not reading bugmail)]

fixed.

Comment 21

[sairuh (rarely reading bugmail)]

*** Bug 24109 has been marked as a duplicate of this bug. ***

Comment 22

[sairuh (rarely reading bugmail)]

verified as fixed on winNT using non-comm bits from 2000-02-04-10.

Comment 23

[Sean Richardson]

*** Bug 25225 has been marked as a duplicate of this bug. ***