72df451bd3
Help with readability by using module.exports and require rather than the MobileFrontend provided mw.mobileFrontend module manager (and avoid adopting webpack at this time) Replace usages of mw.mobileFrontend.require with local require and module.exports (compatible with RL or Node implementation) Changes: * Notifications modules are merged into skins.minerva.scripts and initialised via a client side check. * new file overlayManager for exporting an overlayManager singleton rather than being hidden inside resources/skins.minerva.scripts/init.js * All M.define/M.requires swapped out for require where possible The `define` method is now forbidden in the repo. Bug: T212944 Change-Id: I44790dd3fc6fe42bb502d79c39c4081c223bf2b1
32 lines
832 B
JavaScript
32 lines
832 B
JavaScript
var MainMenu = require( './menu/MainMenu.js' ),
|
|
mainMenu = createMainMenu();
|
|
|
|
/**
|
|
* Creates an instance of the `MainMenu`, using the `wgMinervaMenuData` for configuration.
|
|
*
|
|
* N.B. that the activator - the UI element that the user must click in order to open the main
|
|
* menu - is always `.header .main-menu-button`.
|
|
*
|
|
* @return {MainMenu}
|
|
*
|
|
* @ignore
|
|
*/
|
|
function createMainMenu() {
|
|
var options = mw.config.get( 'wgMinervaMenuData', {} );
|
|
|
|
options.activator = '.header .main-menu-button';
|
|
|
|
return new MainMenu( options );
|
|
}
|
|
|
|
$( function () {
|
|
// eslint-disable-next-line no-jquery/no-global-selector
|
|
if ( !$( '#mw-mf-page-left' ).find( '.menu' ).length ) {
|
|
// Now we have a main menu button register it.
|
|
mainMenu.registerClickEvents();
|
|
mainMenu.appendTo( '#mw-mf-page-left' );
|
|
}
|
|
} );
|
|
|
|
module.exports = mainMenu;
|