$.contextMenu is a management facility for - you guessed it - context menus. It was designed for an application where there are hundreds of elements that may show a context menu - so intialization speed and memory usage are kept fairly small. It also allows to register context menus without providing actual markup, as $.contextMenu generates DOMElements as needed.

features - demo - documentation

• jQuery >=1.8.2
• jQuery UI position (optional but recommended)

register contextMenu from javascript:

$.contextMenu({
    // define which elements trigger this menu
    selector: ".with-cool-menu",
    // define the elements of the menu
    items: {
        foo: {name: "Foo", callback: function(e, key, currentMenuData){ alert("Foo!"); }},
        bar: {name: "Bar", callback: function(e, key, currentMenuData){ alert("Bar!") }}
    }
    // there's more, have a look at the demos and docs...
});

have a look at the demos.

Version 3.0 is a restructure of the javascript into something more sane written in ES6. It consolidates all API's so callbacks are better documented and more concise. The basics are still the same, but all callbacks are structured differently.

The goal of this refactor was mostly to make the ContextMenu easier to maintain, and make the API's more consise. It also adds JSdoc comments so the API documentation is generated from the code and it enables code completion.

Code coverage is also introduced in the test suite.

If you really want you can also use the ContextMenu class to instantiate the menu objects instead of the jQuery calls. It still requires jQuery to function.

import {ContextMenu, ContextMenuItemTypes} from 'jquery-contextmenu';
const contextMenu = new ContextMenu();
contextMenu.create({
    // define which elements trigger this menu
    selector: ".with-cool-menu",
    // define the elements of the menu
    items: {
        foo: {name: "Foo", callback: function(e, key, currentMenuData){ alert("Foo!"); }},
        bar: {name: "Bar", callback: function(e, key, currentMenuData){ alert("Bar!") }}
    }
    // there's more, have a look at the demos and docs...
});

Check out the documentation for 3.0-beta for more information.

Update June 2017: The <menu> element has been deprecated in the html spec because of lack of support. This means the menu element won't be coming to browsers anymore, and the polyfill part of this menu is now deprecated.

Firefox 8 implemented contextmenu using the <menuitem> tags for menu-structure. The specs however state that <command> tags should be used for this purpose. $.contextMenu accepts both.

Firefox 8 does not yet fully implement the contextmenu specification (Ticket #617528). The elements a, button, input and option are usable as commands are being ignored altogether. It also doesn't (optically) distinguish between checkbox/radio and regular commands (Bug #705292).

• contextmenu specs
• command specs
• Browser support according to caniuse.com

Note: While the specs note <option>s to be renderd as regular commands, $.contextMenu will render an actual <select>. import contextMenu from HTML5 <menu>:

$.contextMenu("html5");

You're (obviously) able to use the context menu with your mouse. Once it is opened, you can also use the keyboard to (fully) navigate it.

• ↑ (up) previous item in list, will skip disabled elements and wrap around
• ↓ (down) next item in, will skip disabled elements and wrap around
• → (right) dive into sub-menu
• ← (left) rise from sub-menu
• ↵ (return) invoke command
• ⇥ (tab) next item or input element, will skip disabled elements and wrap around
• ⇪ ⇥ (shift tab) previous item or input element, will skip disabled elements and wrap around
• ⎋ (escape) close menu
• ⌴ (space) captured and ignore to avoid page scrolling (for consistency with native menus)
• ⇞ (page up) captured and ignore to avoid page scrolling (for consistency with native menus)
• ⇟ (page down) captured and ignore to avoid page scrolling (for consistency with native menus)
• ↖ (home) first item in list, will skip disabled elements
• ↘ (end) last item in list, will skip disabled elements

Besides the obvious, browser also react to alphanumeric key strokes. Hitting r in a context menu will make Firefox (8) reload the page immediately. Chrome selects the option to see infos on the page, Safari selects the option to print the document. Awesome, right? Until trying the same on Windows I did not realize that the browsers were using the access-key for this. I would've preferred typing the first character of something, say "s" for "save" and then iterate through all the commands beginning with s. But that's me - what do I know about UX? Anyways, $.contextMenu now also supports accesskey handling.

• Björn Brala
• Rodney Rehm (original creator)
• Christiaan Baartse (single callback per menu)
• Addy Osmani (compatibility with native context menu in Firefox 8)

Font-Awesome icons used from encharm/Font-Awesome-SVG-PNG.