38403 - Enter should only choose menu option if mouse is not down

Status: NEW

(Core :: XUL, defect, P3)

Description

[Blake Ross]

Build ID: 2000050608

All win32 apps behave in the following way:
  
  * If a menu item is selected and the left mouse button is up, pressing enter
    will act like a click and choose that menu item.

  * If a menu item is selected and the left mouse button down, pressing enter
    will do nothing.

In Mozilla, pressing the enter chooses the item regardless of whether the mouse 
button is down or not.

Steps to reproduce:

(1) Left-click on "File", don't let go of the mouse button.
(2) Navigate down to "Open File...", with the mouse button still down.
(3) Press enter.

The Open File native dialog appears.

Comment 1

[Blake Ross]

Joki, is this you?

Comment 2

[Mike Pinkerton (not reading bugmail)]

sure.

Comment 3

[Peter Trudelle]

Mass-moving all M20-M30 XPToolkit bugs to Future

Comment 4

[sairuh (rarely reading bugmail)]

*spam*: transferring current XP Menu bugs over to jrgm, the new component owner.
feel free to add me to the cc list (unless am the Reporter) of any of these, if
you have any questions/etc.

Comment 5

[Blake Ross]

cc dean

Comment 6

[:deanis74]

Simple to fix.  But first I have to figure out how to get the mouse state.  
Anyone want to save me some searching time?

Comment 7

[:deanis74]

Huh, I don't even remember writing that comment.  Anyway, the behavior in 
Windows is actually that none of the access keys nor Enter nor Esc work when the 
left mouse button is down in a menu, or either the left or the right mouse 
button in a context menu.

Should this be done for all platforms?  It's a pretty unusual case, and I think 
wouldn't make much difference if we did.

Comment 8

[:deanis74]

So, anyone know of an XP way to determine whether a mouse button is currently
pressed?

Comment 9

[Thomas]

Is this bug still a real problem?
There was no action since 04-2001, maybe someone can just close this bug?

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.