Jeegoocontext, a jQuery contextmenu plugin

Jeegoocontext is a jQuery plugin that allows for multiple custom contextmenus (pop-up menus) to exist on a single page. The plugin is able to transform any unordered list appended to the body into a multi-level, intelligently positioned styled contextmenu via a single call.

JeeGooContext is released under the MIT license.

demo

• Home
• Planit works
• Jeegoocontext

Release table

Features

• Easy to implement.
• Both vertical and horizontal intelligent positioning.
• Customizable time delays to provide easy selection of items.
• Multiple context menus on a single page.
• Fully css customizable UI.
• Customizable behavior via callbacks.
• Customizable class names to avoid potential naming conflicts.
• Opera compatible.
• Cross-browser support.
• Keyboard support.
• Lightweight.

Easy to implement

Steps required to implement the plugin:

1. Include references to the jquery library, and to jquery.jeegoocontext.min.js.
2. Select a skin (skins cm_default and cm_blue included in the code-download) and include a reference to the skin's stylesheet.
3. Append an unordered list to the body and give it a unique id and the following class name: "jeegoocontext" and the class name for the skin: "cm_default" or "cm_blue" for example.
4. Bind any context to the menu with the following call: $('context').jeegoocontext('menu id'); Where 'context' can be any jQuery selector and 'menu id' contains the unique id of the menu, for example: $('.context').jeegoocontext('menu_1');

Both vertical and horizontal intelligent positioning

Normally the context menu opens exactly at the clicked position. However, when opened at the near edges of a webpage, the menu and subsequent submenus are offset to the left/top to avoid overflow to the right/bottom.

Overflow behavior can be customized by adjusting the widthOverflowOffset and heightOverflowOffset properties on the options object.

Customizable time delays to provide easy selection of items

The delay property on the options object provides time-out values to the menu to allow for easy selection of submenu items. Without these delays expanded submenus collapse immediately after a user moves his/her mouse to another list-item, which can be very annoying. The following animations illustrate these conditions:

No delays

Delays

Fully css customizable UI

The plugin contains very little presentation script, so the UI can be fully styled via css. The code-download includes a skins folder containing two skins named: "cm_default" and "cm_blue". These skins consist of nothing more than an images folder and a stylesheet.

Customizable behavior via callbacks

The plugin publishes the following four useful events to provide customizable behavior:

1. onShow
2. onHover
3. onSelect
4. onHide

From within each of these callbacks default behavior can be cancelled by returning false.

Customizable class names to avoid potential naming conflicts

The plugin uses the following class names:

1. active
2. hover
3. jeegoocontext
4. submenu
5. separator

All class names are overridable to avoid potential naming conflicts.

Opera compatible

Older versions of Opera don't allow right-click event overrides. When the plugin detects older versions of Opera it automatically binds the menu to the ctrl+click event. The event-type can be overriden via the operaEvent property on the options object.

Cross-browser support

The plugin was tested in the following browsers: Opera 10, Safari 4, Chrome 3, Firefox 3, Internet Explorer 6, 7 & 8. Apart from some minor bugs in IE 6 and IE7, the menu works in all these browsers.

Keyboard support

The escape key closes the menu. The enter key selects a menu-item. The arrow keys can be used to move between different menu-items and submenus. Both the up and down arrow keys can be hold down to loop through the menu-items.

Lightweight

The minified version of the script is just under 7 kb in size.

Peter,16-11-2009 @ 21:30

Cool. I had the context menu up and running in a couple of minutes. Good work.

Joe,20-11-2009 @ 11:59

Hey. This looks good. How hard would it be to have it be a pop-up menu rather than context? (In other words, to use the left-click...) Should be an easy change?

Erik,20-11-2009 @ 15:49

Hey Joe, the latest release (version 1.1.1) exposes an event property on the options object which can be used to bind the menu to a different event. For example, the menu can be bound to a left-click like this: $('.context').jeegoocontext('menu', { event: 'click' });

pako,21-11-2009 @ 14:56

This line in the style.css for the cm_default theme needs fixing: /* Possibly inherited values overrides */ border-width:0; float:none; background-color:#d7e1eb; background:#e6e6e6 url(images/contextmenu_bg.gif) repeat-y 0 0; I just removed the reference to the contextmenu_bg.gif file in my version.

pako,22-11-2009 @ 11:53

Jeegoo Context doesn't property support adding the same multi-level context menu to dynamically generated elements being added to the document on-the-fly.

pako,22-11-2009 @ 11:54

I have a single context menu and try adding it to every new element the user adds to the document. I call the following method: $('#element_'+el.id).jeegoocontext('contextmenu');

pako,22-11-2009 @ 11:55

Every time this happens Jeegoo Context adds another arrow next to each element with a submenu.

Erik,23-11-2009 @ 10:19

Hey pako, thanks for the info. I hadn't considered dynamically added elements when designing the menu. There should obviously be a check if submenu arrows are already present before adding them. I will fix these issues in the next release.

K,28-11-2009 @ 04:41

Great work. But how can I unbind the plugin's events...?

K,28-11-2009 @ 05:11

> pako Simple (temporary) solution Line 101 <Before> if(_menus[id].autoAddSubmenuArrows)$('#' + id).find('li:has(ul)').prepend('span class="' + _menus[id].submenuClass + '"/span'); <After> if(_menus[id].autoAddSubmenuArrows && !$('#' + id).find('span.submenu').length)$('#' + id).find('li:has(ul)').prepend('span class="' + _menus[id].submenuClass + '"/span');

Denis,07-12-2009 @ 07:54

Hey. Thanks for a great plugin! I am using this plugin for showing both context and standard menus. The latter, however, is usually shown when a button is pressed. Therefore, it would be great if you add to your plugin an ability to bind the top left corner of a menu not only to current pointer coords, but also to a DOM element coords (in my case I would bind it to the bottom left corner of a button so the menu would appear just below that button). Thanks again for your work!

Denis,08-12-2009 @ 08:28

Hi, it's me again. I've just found a bug in the plugin: if a submenu doesn't have a fixed width (width:auto), then the plugin incorrectly calculates the left offset. The wider a submenu the more far from the root menu it will appear, regardless of the submenuLeftOffset parameter. Hope this info would be helpful and the bug will be fixed soon!

Denis,08-12-2009 @ 10:27

Here's the fix to the bug I've found. Replace the code at string 164 with the one below: 'left': (overflow.width > 0) ? (-$submenu.parent().parent().width() - _menus[id].submenuLeftOffset + 'px') : ($submenu.parent().parent().width() + _menus[id].submenuLeftOffset + 'px'), Erik, you should calculate the offset for a submenu using the width of its parent, not itself. Because, like in my case, the parent's width was less than the submenu's and thus the submenu appeared the more far from the parent menu the wider that submenu was.

Erik,09-12-2009 @ 12:21

Hi Denis, i'm glad you like the plugin. I'll look into these issues asap.

Denis,13-12-2009 @ 18:15

Hi Erik. I've made some improvements to your plugin. How can I contact you to send that modified version of the plugin to you?

Gerd,14-12-2009 @ 19:01

Hi Erik, we found a bunch of performance problems when using a lot of contextmenus on a single site. Within the jegoocontext-function you are registering the events onmouseover and onclick on the $(document) element for each menu - even if it's not yet open. We're using your menu in an ajax-powered application and so every postback registers us several new events and makes the menu very slow. A suggestion to work a round this problem would be to move the block starting with $(document).mouseover(function(e){ to the position immediately below the // Fade-in menu at clicked-position. $menu.css({ 'left': e.pageX + 'px', 'top': e.pageY + 'px' }).fadeIn(_menus[id].fadeIn); statement. This causes the event to be registered only when needed (when the menu pops up). Also it would be great to unregister the events as soon as the menu closes. Thanks for your great menu component and i hope you will be able to implement my feedback best regards Gerd

Erik,17-12-2009 @ 13:29

Denis, you can send the modified version to info at planitworks.nl.

Erik,17-12-2009 @ 13:45

Gerd, thanks for the feedback. I'm aware of the multiple events registered on the document, but i haven't had time to fix this. Your solution sounds good though.

John Dell,19-12-2009 @ 00:47

Hi, I like this plugin, but I want to use it in an application that also uses prototype (for awhile until fully transitioned to jQuery), so I need to use jQuery.noConflict(); which means all the $ commands need to change to jQuery. This is standard for common jQuery plugins, so I'd recommend changing this. Thanks! John

Peter,19-12-2009 @ 11:29

@John. Wrapping the code with (function($) { })(jQuery);. No need to use jQuery.noConflict for this plugin. The $ name is scoped to refer to the jQuery object.

pay,23-12-2009 @ 07:28

do you know ? how to make contextmenu in jquery and Intergret to Zk ?

MikeS,24-12-2009 @ 16:38

How would I go about making a menu option appear disabled?

Peter,27-12-2009 @ 11:50

@pay, include the jquery library and the contextmenu script. You can use jQuery to make decisions or use your Zk framework.

Peter,27-12-2009 @ 11:53

@MikeS, use the onshow callback to hide you elements. You can select your elements using jQuery and hide them.

Nick,28-12-2009 @ 21:02

I would like to have the Escape key close the menu just like normal Windows UI. I'm sure I can use the onShow callback, but it should probably be a built-in function.

John,06-01-2010 @ 21:04

Would you consider moving this project to github and maybe adding a google group for users to discuss this? I think you will find more patches and more and happier users. This is a great plugin! Thanks, John

John,06-01-2010 @ 21:16

@Peter, thanks, the plugin is working fine even when I have prototype. my mistake. Thanks! Only problem I'm having is that when I right click, unless I hold down the right mouse button until the mouse is *over* the menu, it will disappear. Once I have moused over the menu, then it will stay regardless of whether I've move the mouse off the menu. Weird. Also, the menu is popping up maybe 5-10px down and right of the tip of the mouse, but in your demos, it opens exactly at the tip of the mouse. Not sure why that is happening. @Nick, the ESC key closes the menu for me using standard setup (no default changes or callbacks).

John,06-01-2010 @ 21:47

ok, so it is exactly 5px down and right. My super-crude hack below (line 250-251) makes it work. I'm sure something in our site css is affecting it. Firebug isn't showing anything meaningful. $menu.css({ 'left': e.pageX - 5 + 'px', 'top': e.pageY - 5 + 'px' }).fadeIn(_menus[id].fadeIn); So, I'll stick with this for now. Thanks!

roger,12-01-2010 @ 22:39

Thanks a lot by this great plugin! I would like to have the ability to use a CSS selector instead of just restrict the usage of the menu's id. Thanks again.

roger,12-01-2010 @ 22:52

And FYI, me too would like to have the Escape key close the menu just like normal Windows UI (it is not working for me on FF3.5/IE8/Chrome 4 - also does not works in the examples).

Erik,17-01-2010 @ 13:20

Roger, why would you want to use another selector instead of an id? The menu selector should only return a single menu because multiple contexts can be mapped to a single menu, but a single context cannot be mapped to multiple menus. Hence the obvious solution would be to select a menu by id.

Erik,17-01-2010 @ 13:28

Keyboard support will probably be integrated into the next release

roger,25-01-2010 @ 22:48

Hey Erik, You are right about the obvious solution is to use the element's id. Thanks!

Catalin David,11-03-2010 @ 01:32

Hello! I've been trying out the context menu for a few days now and I am decided to use it in an academic project I am working on. Still, I have one question / request regarding dynamically generated menu entries: is this possible (and if yes, how?)? For example, I would create just an empty ul (with proper class attributes) element at the end of the body that I would fill later on, depending on where the user clicks with options available for that context. I've tried to add li elements from JavaScript, they appear on the menu, but the events do not get triggered (which rather defeats the purpose of a context menu). I would really appreciate if you could implement/fix this and, if not, at least give me some hints on how to implement it (though, I am rather novice with JS and jQuery). Thanks for this tool, Catalin

Erik,12-03-2010 @ 17:41

Hi Catalin, If i understand you correctly, you want to view different menu-options depending on the clicked context. To achieve this you can either use multiple contextmenus, one for each context. Or you can use the onShow callback to show/hide menu items on the fly, depending on the context, for example like this: onShow: function(e, context){ // Show or hide menu-items based on context id. switch($(context).attr('id')) { case 'context1': $('#[MENU_ID] li.context2, #[MENU_ID] li.context3').hide(); $('#[MENU_ID] li.context1').show(); break; case 'context2': $('#[MENU_ID] li.context1, #[MENU_ID] li.context3').hide(); $('#[MENU_ID] li.context2').show(); break; case 'context3': $('#[MENU_ID] li.context1, #[MENU_ID] li.context2').hide(); $('#[MENU_ID] li.context3').show(); break; } } For this to work, you need to append just one contextmenu to the body consisting of all possible menu-options. I hope this helps.

Erik,12-03-2010 @ 19:33

You can view an example via "Examples, onShow callback alternative".

Tom,16-03-2010 @ 00:26

This is an amazing plugin - was so simple to get it up and running... great work! I couldn't find any information about licensing?

Tom,16-03-2010 @ 00:29

Well of course as soon as I posted that, I found the information about licensing in the code itself. Thanks again!

Gregory,20-03-2010 @ 23:50

Hi. I'm trying to use your plugin but I don't need it to pop after a right click. Is there a way to remap it on a left click? Thanks in advance.

Gregory,21-03-2010 @ 00:08

Oh, I found it in the documentation. I'm so inattentive lol.

Simon,21-03-2010 @ 14:42

This is an awesome plugin. I seem to have hit an anomoly though. The menu pop up does not appear near the mouse, it is offset to the right. The top and left properties are being set, presuambly by the plugin. It doesn't seem to be calculating the correct position. It is something to do with the margin:auto and centering of the content on the page. If i resize the browser window so the content is shown (no edge around the page) then the menu is the right place. The further expanded the window is, the further the menu is popping up from the mouse click point. Anything can be done to fix this? Many thanks

Erik,04-04-2010 @ 12:10

Hi Simon, make sure to append the contextmenu(ul) directly to body and be certain no style rules interfere with the menu's style.

XRumerTest,04-04-2010 @ 15:31

Hello. And Bye.

Ron,08-04-2010 @ 17:25

Could you please provide details on licensing option?

Erik,18-04-2010 @ 20:27

The plugin is dual licensed under the MIT and GPL licenses.

Erik,24-04-2010 @ 20:53

Version 1.2.2 is released, which includes keyboard support.

cStestiato,21-05-2010 @ 03:17

Thank you very well read allss textt about drsating and ilike it very much

Jack,09-06-2010 @ 17:38

I think I allready have been told about this subject at pub 2 days ago by a friend, but at that time it didn't caugh my attention.

Yafeng,13-07-2010 @ 13:07

I'm not sure about dual license mode. Is it licensed under MIT OR GPL,or MIT AND GPL?

rolaca11,24-07-2010 @ 14:56

I want to ask you about how can (if it's possible) I give new icons to the context menu? Please e-mail me!

Erik,24-07-2010 @ 17:42

@Yafeng, MIT Or GPL

Erik,24-07-2010 @ 17:45

@rolaca11, icons are purely controlled by css. You can add a custom icon to the menu by prepending a span to the desired menu-item like this: <li class="icon"> <span class="icon MYCUSTOMCLASS"></span> (MENU-ITEM TEXT) </li> Next, copy your icon to the images/icons folder of the skin folder of your choice, for example "jeegoocontext/skins/cm_default/images/icons". Finally, add the following css-rule to your skin's stylesheet("jeegoocontext/skins/cm_default/style.css"): body ul.cm_default span.MYCUSTOMCLASS{background-image:url(images/icons/MYCUSTOMICON.gif)}

rolaca11,24-07-2010 @ 19:49

actually, before writing this post, i have tried with exactly the same, and didn't work. I tried it now too, with the same result. :(

rolaca11,24-07-2010 @ 20:17

I managed, to solve the problem, I forgot to upload the new files :)

Henrik,04-08-2010 @ 15:18

I really dig this menu but I need to position the popup differently than the standard behavior. I want to trigger the popup from a button (with left click) and open the pop up below the button. It would be nice to give an element as a position reference for the popup and also be able to add optional horizontal and vertical offsets from the element position. Do you think you can implement that in a future release?

Malith,10-08-2010 @ 04:19

Hi Erik, this is actually great. i'm using it with my application. in my case i need to disable the context menu when i show a hidden dialog on screen. how can i disable and re-enable the context menu? please help me.

Erik,16-08-2010 @ 09:57

@Henrik, i can probably integrate this behavior into the next release. @Malith, the context menu can be disabled permanently for a certain context by calling: $(context).nojeegoocontext(); The best way to temporarily disable the context menu is to (conditionally) return false in the onShow callback like this: $(context).jeegoocontex(myMenu, {onShow: function(e, context){ if(myDialogVisible)return false;}}

Sean,30-08-2010 @ 01:33

Hi, it is possible to dynamically populate the menu/submenu items? In my application the submenu items will be retrieved via an AJAX request.

Luc,13-09-2010 @ 06:52

I have two submenus: "insert" and "append". From onShow, depending on the context, I show the ul containing the right "insert" submenu options, and I hide the other ones. Then i use .html() to copy the visible ul from "insert" to "append" submenu.. the submenu is displayed normally but hover is not added automatically to "append" submenu options.. It would be logical you bind events to menu items after onShow()

Erik,15-09-2010 @ 09:25

@ Sean @ Luc, currently there is no support to dynamically add menu-items to an already initialized menu. I hope i can fix this in the next release.

Sergio,20-09-2010 @ 11:44

Opera v10.50 allow mouse right-click!!!

Luc,20-09-2010 @ 19:51

Erik: for my specific problem it works, just had to use .clone(true) to copy the submenu with the events bindings... It is also possible yet to hide or show menu items or submenus, or to change existing options text from onShow() depending on the context.

Paul,30-09-2010 @ 22:26

Great plugin! Is there a way to open the menu from a custom event triggered from JQuery. (i.e. $('#mydiv').trigger('customEvent');)? thanks!

Erik,03-10-2010 @ 12:57

@ Sergio, the new version which is soon to be released contains better support for newer versions of Opera. The current version relies on browser sniffing to detect Opera, the new version relies on feature detection.

Erik ,03-10-2010 @ 13:05

@ Paul, the menu can be opened via trigger but you need to provide it with an event object with the pageX and pageY properties set:

var e = $.Event('contextmenu');
e.pageX = 500;
e.pageY = 500;
$('myContext').trigger(e);

Leonard,15-10-2010 @ 13:21

Great plug-in sadly it is not IE 9 compatible. The problem is that the e.pageX and e.pageY values remain undefined and the offset values as well. Therefore the menu position doesn't get updated and shown. I wasn't able to come up with a good solution to get these values defined, but I hope someone will find an easy fix.

Erik,24-10-2010 @ 20:57

If e.pageX and e.pageY remain undefined in IE9, i think a lot of plugins are going to have trouble with IE9 as they are normalized properties of the jquery event object. I'll look into this issue as soon as IE9 is out of beta.

Leonard,26-10-2010 @ 14:09

IE 9 seems to handle event completely different than before, so it really is a burden. I hope JQuery can quickly find a way to standardize this again, probably the plugin will start functioning like normal again. For now I forced IE 8 compatibility mode, however I have to give up on some of the features I would like to use in IE 9. Hope the JQuery team soon implements a solution.

Stefan,10-11-2010 @ 21:50

Thank you very much for your wonderful plugin. I had the same issue with the wrong position when the menu div is not in the body element. I sent you the modified working version and hope it will be of use for you.

Luc,13-11-2010 @ 09:07

Thanks for your work. I sent you a patch for version 1.3, allowing to release the right mouse button to select an option, for standard contextmenu behaviour compliance. Regards

Luc,15-11-2010 @ 10:21

I changed the mouseup behaviour to match exactly google chrome's one (Before delay, don't select any option when mouse didnt move nor hide menu when mouseup occurs outside). You can get the patch on pastebin.com/eD2bhnbb

Moiz,19-11-2010 @ 12:00

Hey, great plugin! I am running into a problem and I have no idea whats going on. On right click the menu does open but it doesn't hide on document click or when I enable autoHide. This is the problem only in firefox 3.6.10 linux. It works great on Chrome. Any suggestions? Thanks!

Luc,22-11-2010 @ 12:19

MOIZ: pastebin.com/V0tnk4cQ ERIK: pastebin.com/W0KgFvd2

Luc,22-11-2010 @ 12:20

50 chars is way too short :-D

mates,04-12-2010 @ 01:13

Hey, good job. But I need help. On the page I have link with the attribute href="javascript: __doPostBack('grid','Sort$ident'), which displays context menu (...jeegoocontext('jg_menu', {event: 'click',...). Is there any way to run the original link event after select an item from the context menu? thanks a lot

Luc,10-01-2011 @ 11:18

Here's the patch for enabling mouseup and adding a 'reset' method to hide the menu with $(document).jeegoocontext('reset'); Also fix a bug where unbind or expire was not called when running jeegoocontext again on the same selector (in that case menu handlers were called many times) http://pastebin.com/SmJ1TJy9 Thanks again !

Niel,10-01-2011 @ 17:31

Great plugin, I Love it... Great work guys... Very easy to implement, few minutes of work and context menu starts working... again great work and thanks for all your effort.

Steffen,04-02-2011 @ 15:16

Thx for this great tool. Two Questions - One: is it possible (maybe in future), to set the position of the menu to a special point of a clickable element (e.g. the menu opens always with the left bottom corner at the right upper corner of a button)? and Two: another nice option would be the opportunity to control the opening direction. Actually with openBelowContext the Menu opens downwards, it woud be nice if I could say open menu upwards. Best Regards Steffen

Memborg,07-02-2011 @ 15:48

Looking forward to IE9 support.

Ryan,04-03-2011 @ 03:46

How can you tell which dom element id was right clicked on?

jonas eriksson,13-03-2011 @ 21:06

Hi, wonderfull plugin and nice that you added the ability to add/remove items in the context menu after init. However, it doesnt work for me :( I have included livequery and even tried to update livequery to the newest version. But when I add "livequery:true" to my menu options, nothing happens when I rightclick, no error, no menu, nothing :( Running Jquery version 1.4.4 and Firefox 3.6.15 It works perfectly without the livequery:true in options so I dont now what to do. Anyone else has the same problem ? One of the demo works (when adding items to the menu "live") so could it be that my jquery version breaks it ?

smit,15-06-2011 @ 13:55

Hi, Is it possible modifiy to right to left dierction languages?

Allie,01-07-2011 @ 02:15

Is there a way to get the properties of the selector? I am using it for a diary and want to find the properties of the selector to customise the context menu. Any suggestions how I can do this from within the script. Thanks.

Allie,01-07-2011 @ 02:35

Found it. Didn't read the documentation properly. ~Duh. For those who did the same mistake as me, its $(context) for the callbacks. BTW, great plugin.

Sam Smith,01-07-2011 @ 16:14

Hi. Love it, but could you please clarify the license - and ideally include a copy in the download. The GPL and MIT are different, with the MIT license being preferred as it is more liberal than the GPL so if we get a choice I prefer the MIT license.

Also maybe the page could link to the licenses?

Lutz,19-07-2011 @ 14:51

Hi. I'd need to raise the same issues as Sam. I would like to use the jeegoocontext commerially which would work with the MIT license but not with GPL (contributing the product to open source is not an option). Could you please clarify which one applies (and of cause I'd like the MIT more ;). Thank you!

Erik,19-07-2011 @ 14:55

You can use either.

Alessandro,22-07-2011 @ 10:42

Can I get the text value of the selector clicked?

Affan,25-07-2011 @ 15:31

This is a lovely plugin. I used it on local host by when I moved it online I experienced a problem: Its main menu appears towards right and bottom of original mouse pointer.

Alex,26-07-2011 @ 11:22

Great work Erik! If I may, I would suggest a small change that might fix menu positioning issues within nested divs, and some jquery plugins (e.g. datatables): // Fade-in menu at clicked-position. $menu.css({ 'position': 'fixed', // I would add this line 'left': startLeft + 'px', 'top': startTop + 'px' }).fadeIn(_menus[id].fadeIn);

Bob,29-09-2011 @ 05:33

Hi Erik ! it appears that there is a bug in IE 7 & IE9 where if you keep right-clicking on the trigger area. it remembers the previous state of the submenus however, it's showing the submenu without the options even the menu is not selected. How do we resolve this issue ?

Bob,29-09-2011 @ 05:43

For example, initially, you select a submenu on the third level submenu and when you right-click again it's showing the third level submenu container without any options and even the parent menu hasn't been selected yet. it looks like it remembers the previous state of the context menu.

sadra,08-10-2011 @ 16:12

Hi, this code fixed for RTL and LTR direction by me, but has a small problem, can you help me to correct it? new modified code sent to "info@planitworks.nl" thanks... i'm wait

Kert,23-12-2011 @ 17:52

Thanks guys, I just about lost it looikng for this.

DanH,02-01-2012 @ 00:16

Is there some way to keep the click event from being swallowed? I have a grid, and I want the click event to do it's normal thing of selecting the row, but also have the context menu pop.

DanH,02-01-2012 @ 00:31

To solve my problem, I'm using the default right-click event, then using the onShow callback to call a click. Feels like a hack, but it's working.

Julian,10-01-2012 @ 15:30

Nice plugin! Any change that the plugin will work with the default 'live' functionality of jQuery instead of the liveQuery plugin?

Steve,08-04-2012 @ 04:54

Perfect guide! I'm only beginning out in mteirakng and advertising and attempting to find out to perform it nicely assets just like this guide are very useful. As our company is primarily based in america, it's all somewhat new to us. 0

Richard,26-05-2012 @ 16:36

This looks really good, but you should prevent browser context menu to appear when you right click in your own context menu ...

Julian,15-11-2012 @ 21:21

Hey Erik, Is this project still active? Maybe you can submit the project to github or something like that? I have some enhancements to commit :)

Erik van den Berg,18-11-2012 @ 12:53

Hi Julian, the project is pretty much on hold right now:(. I'll look into GitHub ASAP...

Comments are closed.