1/** 2 * @file 3 * Mobile navigation behavior definition. 4 * 5 * Get fron Drupal the settings specified on mobile navigation administration page 6 * and place them in a parameters structures to run the Mobile Menu plugin. 7 */ 8 9(function($) { 10 // Execute mobile-navigation construction with the settings on mobile_navigation. 11 Drupal.behaviors.mobile_navigation = { 12 attach: function(context) { 13 /*********** REMOVE THIS ***********/ 14 $("body").prepend("<div id='debugInfo'></div>"); 15 $("#debugInfo").css({ 16 position : "fixed", 17 right : "50px", 18 top : "50px" 19 }); 20 /*******************************/ 21 /******** Move mobile navigation menus to the body directly. *********/ 22 $("#mobile-navigation-menus").appendTo("body"); 23 /******** Setting *******/ 24 var configurations = Drupal.settings.mobile_navigation.configurations, 25 displays = Drupal.settings.mobile_navigation.displays, 26 module_path = Drupal.settings.mobile_navigation.module_path; 27 for(menu_display in configurations) { 28 var data = { 29 'configuration': configurations[menu_display], 30 'display_definitions' : displays, 31 'name' : menu_display, 32 'files_path' : module_path + '/js/', 33 }; 34 /* The keys of the configurations array is the same classes used for the menus. */ 35 $("#" + menu_display + " ul", context).mobile_menu(menu_display, data); 36 } 37 } 38 } 39})(jQuery);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.