1/** 2 * All of the code for your public-facing JavaScript source 3 * should reside in this file. 4 * 5 * Note: It has been assumed you will write jQuery code here, so the 6 * $ function reference has been prepared for usage within the scope 7 * of this function. 8 * 9 * @package Payment_Reminder 10 * 11 * This enables you to define handlers, for when the DOM is ready: 12 */ 13 14(function( $ ) { 15 'use strict'; 16 17 /** 18 * All of the code for your public-facing JavaScript source 19 * should reside in this file. 20 * 21 * Note: It has been assumed you will write jQuery code here, so the 22 * $ function reference has been prepared for usage within the scope 23 * of this function. 24 * 25 * This enables you to define handlers, for when the DOM is ready: 26 * 27 * $(function() { 28 * 29 * }); 30 * 31 * When the window is loaded: 32 * 33 * $( window ).load(function() { 34 * 35 * }); 36 * 37 * ...and/or other possibilities. 38 * 39 * Ideally, it is not considered best practise to attach more than a 40 * single DOM-ready or window-load handler for a particular page. 41 * Although scripts in the WordPress core, Plugins and Themes may be 42 * practising this, we should strive to set a better example in our own work. 43 */ 44 45})( 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.