File tree Expand file tree Collapse file tree 1 file changed +10
-10
lines changed
Expand file tree Collapse file tree 1 file changed +10
-10
lines changed Original file line number Diff line number Diff line change 55 * All of the code for your public-facing JavaScript source
66 * should reside in this file.
77 *
8- * Note that this assume you're going to use jQuery, so it prepares
9- * the $ function reference to be used within the scope of this
10- * function.
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.
1111 *
12- * From here, you're able to define handlers for when the DOM is
13- * ready:
12+ * This enables you to define handlers, for when the DOM is ready:
1413 *
1514 * $(function() {
1615 *
1716 * });
1817 *
19- * Or when the window is loaded:
18+ * When the window is loaded:
2019 *
2120 * $( window ).load(function() {
2221 *
2322 * });
2423 *
25- * ...and so on .
24+ * ...and/or other possibilities .
2625 *
27- * Remember that ideally, we should not attach any more than a single DOM-ready or window-load handler
28- * for any particular page. Though other scripts in WordPress core, other plugins, and other themes may
29- * be doing this, we should try to minimize doing that in our own work.
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.
3030 */
3131
3232} ) ( jQuery ) ;
You can’t perform that action at this time.
0 commit comments