Skip to main content

Search and Top Navigation

#8790 closed feature (invalid)

Opened November 08, 2012 12:35PM UTC

Closed November 23, 2012 08:52AM UTC

Last modified July 02, 2015 08:50AM UTC

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.

Attachments (0)
Change History (6)

Changed November 08, 2012 12:44PM UTC by scottgonzalez comment:1

owner: → 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.

Changed November 08, 2012 12:56PM UTC by Patrik comment:2

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.

Changed November 08, 2012 01:00PM UTC by scottgonzalez comment:3

status: newpending

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

Changed November 23, 2012 08:52AM UTC by trac-o-bot comment:4

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!

Changed May 06, 2014 01:11PM UTC by AmericanUmlaut comment:5

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.

Changed July 02, 2015 08:50AM UTC by ashraf_sabry_m comment:6

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.