jQuery contextMenu v3.0.0 Release Notes
Release Date: 2018-03-16 // almost 7 years agoPrevious changes from v3.0.0-beta.1
-
Migrating
- ๐ To migrate, you only need to change all callback functions to the new arguments (
icon
,build
,visible
,disabled
, itemcallback
and global itemcallback
). Also if you listen tocontextmenu
events, please check if you still get the correct data.
๐ Changed
- ๐ Restructured the code to use Webpack with Babel. Build the code with
yarn run webpack
. - ๐ Changed linting to ESLint.
- ๐ Moved to BrowserStack for browser testing.
- โ Added JSDoc for generated API documentation.
- โ Added 3.x documentation on GitHub pages.
- The previous
opt
androot
arguments are now described ascurrentMenuData
androotMenuData
, which are documented in ContextMenuData. - Defined a few callback types to illustrate the arguments with which they are called.
- ๐ Build callback ContextMenuBuildCallback is now
function(e, $currentTrigger)
. - Icon callback ContextMenuIconCallback is now
function(e, $item, key, item, currentMenuData, rootMenuData)
. - The visibile, disabled, global callback and item callback ContextMenuItemCallback is now
function(e, key, currentMenuData, rootMenuData)
. - If you define custom menu item types in
$.contextMenu.types
they get called as ContextMenuItemTypeCallback withfunction(e, item, currentMenuData, rootMenuData)
. - All events should always include event data containing the ContextMenuData as described in ContextMenuEvent. So if you listen to
contextmenu
events you should always have the data available.
๐ Fixed
- โ Add options argument to events.activates. (Issue #580)
- ๐ Fix support for
$(element).contextMenu('update')
which was broken. - ๐ Fixed bug in checking visibility of items for menu visibility. If a menu item was defined as
{ item: { visible: false } }
it would not stop the menu from showing.
- ๐ To migrate, you only need to change all callback functions to the new arguments (