Open Bug 136634 Opened 22 years ago Updated 2 years ago

Shift+F10/Ctrl+Space/windows' Context-menu key a second time (more than once) should NOT close the context menu

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

defect

Tracking

()

People

(Reporter: mpt, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: access)

To reproduce:
1.  Focus the content area, if it is not focused already.
2.  Type Ctrl+Space (Mac OS) or Shift+F10 (Linux), so that the shortcut menu
    opens.
3.  Type Ctrl+Space or Shift+F10 again.

What should happen:
*   The menu closes.

What happens:
*   Nothing.

Problem occurs with:
*   build 2002040508, Mac OS 9.2
*   build 20020404, Red Hat Linux 7.2

Problem does not occur with:
*   build 2002040903, Windows 2000
On Windows 98:

- With the context menu key, pressing it again doesn't make the context menu
close.  This is how other Windows apps work.

- With Shift+F10, pressing it again makes the context menu close, but pressing
it a third time doesn't make the context menu reappear.  Pressing it a fourth
time makes it reappear.
Jesse: I just noticed the Shift+F10 bug on Windows.  I'd file a new bug on that,
I think it's separate from this one.
still true on linux?

same thing still happens for windows' context menu key - second press doesn't close the menu

(In reply to comment #1)
> On Windows 98:
> - With Shift+F10, pressing it again makes the context menu close, but pressing
> it a third time doesn't make the context menu reappear.  Pressing it a fourth
> time makes it reappear.

filed bug 371777
Assignee: hyatt → nobody
Severity: trivial → normal
Component: XP Toolkit/Widgets: Menus → Keyboard: Navigation
Keywords: access
QA Contact: shrir → keyboard.navigation
Summary: Shift+F10/Ctrl+Space a second time should close the shortcut menu → Shift+F10/Ctrl+Space/windows' Context-menu key a second time should close the context menu
Aaron, is there a UI spec on how this should perform?

Focus: In FF2 and Thunderbird 2, the second shift+F10 now closes the menu, but focus does not revert to original location.  On windows, do two shift+F10 and then spacebar and you see focus is on the titlebar's window control, top left.

linux - where is focus after second shift+F10?
Blocks: 371777
Shift+F10 or the context menu key do not close a context menu in GTK2 apps, so it also shouldn't do so in Mozilla apps on Linux.
MPT says the menu should close, but the consensus on IRC seems to be that the menu should stay up.  Except MAC, rbgray "thinks that is an unspecified combination, there's probably a UI spec"

Neil says "it should stay open on Windows".   Kairo says "we should do whatever the native toolkit does - if it leaves the cpontext menu open, we should do so as well".  Reiterating comment 0, "context key" on windows keyboard does exactly that, context menu doesn't go away  (MSword, etc)

FWIW
* plain old F10 in all the apps I tested just toggles focus on the menu bar
* safari ignores ctrl+space (per rbgray)

Robert, are you saying current linux mozilla does close menu?
Summary: Shift+F10/Ctrl+Space/windows' Context-menu key a second time should close the context menu → Shift+F10/Ctrl+Space/windows' Context-menu key a second time (more than once) should NOT close the context menu
MAC:
Ctrl+Space currently totally broke in cocoa - bug 357540
not sure how/if bug 34572 plays in at all.
Depends on: 357540
Since bug 357540 is fixed this is WFM with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b5pre) Gecko/2008030404 Minefield/3.0b5pre ID:200803040

Does this still occur under Windows and Linux?
Pressing Shift+F10 twice under Windows correctly closes the context menu. But doing the same with the context menu key it doesn't work.
perhaps I messed up my keyboard, but ctrl+space isn't doing anything.
No longer blocks: 371777
Depends on: 371777
Wayne, Ctrl+Space is exclusively for OS X and doesn't work on Windows or Linux.
Component: Keyboard: Navigation → User events and focus handling
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.