1(function() { 2 'use strict'; 3 4 /** 5 * All of the code for your public-facing JavaScript source 6 * should reside in this file. 7 * 8 * Note: It has been assumed you will write jQuery code here, so the 9 * $ function reference has been prepared for usage within the scope 10 * of this function. 11 * 12 * This enables you to define handlers, for when the DOM is ready: 13 * 14 * $(function() { 15 * 16 * }); 17 * 18 * When the window is loaded: 19 * 20 * $( window ).load(function() { 21 * 22 * }); 23 * 24 * ...and/or other possibilities. 25 * 26 * Ideally, it is not considered best practise to attach more than a 27 * single DOM-ready or window-load handler for a particular page. 28 * Although scripts in the WordPress core, Plugins and Themes may be 29 * practising this, we should strive to set a better example in our own work. 30 */ 31 32 33 jQuery(document).ready(function($) { 34 35 $('.lgx-logo-carousel').each(function(){ 36 var $logoitem = $(this); 37 var dataAttr = $logoitem.data(); 38 //console.log(dataAttr.navlarge); 39 var logocarouselParams = { 40 addClassActive:true, 41 responsiveClass:true, 42 loop:dataAttr.loop, 43 dots:dataAttr.dots, 44 autoplay:dataAttr.autoplay, 45 lazyLoad: dataAttr.lazyload, 46 slideTransition: 'linear', 47 autoplayTimeout:dataAttr.autoplaytimeout, 48 autoplaySpeed: dataAttr.autoplayspeed, 49 margin:dataAttr.margin, 50 autoplayHoverPause:dataAttr.autoplayhoverpause, 51 navText :['<img src="'+logosliderwp.owl_navigationTextL+'" alt="Left"/>','<img src="'+logosliderwp.owl_navigationTextR+'" alt="Right"/>'], 52 responsive:{ 53 // Item in Mobile Devices (Less than 768px) 54 0:{ 55 items:dataAttr.itemmobile, 56 nav:dataAttr.navmobile 57 }, 58 // Item in Tablets Devices (768px and Up) 59 768:{ 60 items:dataAttr.itemtablet, 61 nav:dataAttr.navtablet 62 }, 63 // Item in Desktops Devices (Desktops 992px) 64 65 992:{ 66 items:dataAttr.itemdesk, 67 nav:dataAttr.navdesk 68 }, 69 // Item in Large Desktops Devices (1200px and Up) 70 1200:{ 71 items:dataAttr.itemlarge, 72 nav:dataAttr.navlarge 73 } 74 } 75 76 }; 77 $logoitem.owlCarousel(logocarouselParams); 78 // 79 }); 80 81 }); 82 83 84 85})();
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.