Skip to content
This repository has been archived by the owner on Dec 14, 2023. It is now read-only.

Commit

Permalink
Merge pull request #342 from LeeRobertsMe/patch-5
Browse files Browse the repository at this point in the history
Update plugin-name-public.js
  • Loading branch information
DevinVinson committed Nov 3, 2015
2 parents 84741e2 + a11edd3 commit 1b487de
Showing 1 changed file with 10 additions and 10 deletions.
20 changes: 10 additions & 10 deletions plugin-name/public/js/plugin-name-public.js
Original file line number Diff line number Diff line change
Expand Up @@ -5,28 +5,28 @@
* All of the code for your public-facing JavaScript source
* should reside in this file.
*
* Note that this assume you're going to use jQuery, so it prepares
* the $ function reference to be used within the scope of this
* function.
* Note: It has been assumed you will write jQuery code here, so the
* $ function reference has been prepared for usage within the scope
* of this function.
*
* From here, you're able to define handlers for when the DOM is
* ready:
* This enables you to define handlers, for when the DOM is ready:
*
* $(function() {
*
* });
*
* Or when the window is loaded:
* When the window is loaded:
*
* $( window ).load(function() {
*
* });
*
* ...and so on.
* ...and/or other possibilities.
*
* Remember that ideally, we should not attach any more than a single DOM-ready or window-load handler
* for any particular page. Though other scripts in WordPress core, other plugins, and other themes may
* be doing this, we should try to minimize doing that in our own work.
* Ideally, it is not considered best practise to attach more than a
* single DOM-ready or window-load handler for a particular page.
* Although scripts in the WordPress core, Plugins and Themes may be
* practising this, we should strive to set a better example in our own work.
*/

})( jQuery );

0 comments on commit 1b487de

Please sign in to comment.