Opened 10 years ago

Closed 10 years ago

Last modified 8 years ago

#8790 closed feature (invalid)

Disable keyboard shortcuts in menu

Reported by: Patrik Owned by: Patrik
Priority: minor Milestone: 1.10.0
Component: Version: 1.9.1
Keywords: Cc:
Blocked by: Blocking:


There are cases when a user want to disable the keyboard shortcuts in An example is when an input field is a part of the menu (could be login).

A simple option to the constructor which defaults to "on" solves this.

Change History (6)

comment:1 Changed 10 years ago by Scott González

Owner: set to Patrik
Status: newpending

A few things:

  • Why are you putting a login form inside a menu?
  • Why would you use strings for a boolean value?
  • Please don't use fiddles as gists.

Can you point to examples of what you're trying to accomplish? I've used sites that have login forms that popup from a button, but never as part of the actual menu system.

comment:2 Changed 10 years ago by Patrik

Status: pendingnew

1) There are serveral cases where a input field could be placed in a menu. It is just a matter of requirements from the product owner. In this case it is in a submenu in a sidebar. The site I'm using it on is but the code is on our staging environment at the moment. Anyway, disabling menu shortcuts is not a bad feature to the plugin and will only improve it.

2) Boolean value, check. I will do it.

3) Sorry for that, i wont do it again.

comment:3 Changed 10 years ago by Scott González

Status: newpending

We still need examples of what you're trying to accomplish. We need to see existing examples.

comment:4 Changed 10 years ago by trac-o-bot

Resolution: invalid
Status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

comment:5 in reply to:  4 Changed 9 years ago by AmericanUmlaut

I stumbled across this ticket while searching for a solution to the same problem. The use case can be seen at, where we include a login form in the menu at top right.

I've patched our version of jquery-ui to support a boolean keyboard_shortcuts option, and I think including the ability to configure such an option is a good idea.

comment:6 Changed 8 years ago by ashraf_sabry_m

I request this feature too. I've put a Telerik TreeView in the menu widget of the autocomplete widget, meaning that I've created a hybrid autocomplete tree, but now I want to disable the menu widget handling of the ↓ and ↑ keys so that I delegate this to the tree control.

I've made it in a hacky way using event capturing, but it will be great if there's some option to disable this feature cleanly.

Note: See TracTickets for help on using tickets.