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 // Search 33 $('#jollity-clear-search').click(function(e) { 34 e.preventDefault(); 35 $('#jollity-search form, #jollity-search').removeClass('active'); 36 $("#jollity-search #search-filter-form-72472 input[type='text']").val(''); 37 }); 38 39 $('#jollity-search-submit').click(function(e) { 40 e.preventDefault(); 41 $('#jollity-search #search-filter-form-72472').submit(); 42 }); 43 44 $('#jollity-search-trigger').click( function(e) { 45 e.preventDefault(); 46 $('#jollity-search form, #jollity-search').addClass('active'); 47 $('#jollity-search .search-field').val('').focus(); 48 }); 49 50 // Search Mobile 51 $('#search-mobile #jollity-clear-search').click(function(e) { 52 e.preventDefault(); 53 $('#search-mobile #jollity-search form, #search-mobile').removeClass('active'); 54 }); 55 56 $('#search-mobile #jollity-search-trigger').click( function(e) { 57 e.stopPropagation(); 58 e.preventDefault(); 59 $('#search-mobile #jollity-search form, #search-mobile, .ms-wrap').toggleClass('active'); 60 $('.ms-wrap').fadeToggle("fast"); 61 $('#search-mobile #jollity-search .search-field').val('').focus(); 62 $("#search-mobile #jollity-search #search-filter-form-72472").remove(); 63 }); 64 65})( 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.