…ad + class options.
- `handleMenuItemClick`: Even when an item is *disabled*, we still consume the *click* user input. It's just that we don't do anything with it...
+ `hideMenu()` is now an extra API.
- `options.monitorBodyEvents` option: (default: `true`) monitor body mouse click events: when the user clicks outside SlickGrid the menu will be destroyed.
Note: more complex applications for which this basic functionality is unsuitable can handle this themselves by calling the `hideMenu()` API when the application logic decides the header menu should go away.
- `destroy()` method should not forget to kill the possibly already created menu attached to the grid container: `hideMenu()` -- otherwise that one would be lingering and load the DOM for no gain at all.
- documentation in the headermenu LESS file
- theming the headermenu LESS file:
Themable entities; see also less/less.js#1706 why we do it this way.
The user can override these settings by specifying the same name, with their choice of value, in the user-defined theme LESS file which should follow this LESS file.
See also: http://stackoverflow.com/questions/18792255/how-to-override-mixins-in-less-css-1-4