I have 5 pages - for ease lets say:
When I load each indivi
You're checking for the wrong events, pageinit and pageshow are what you should be concerned about.
pageinit fires everytime a page is loaded for the first time, jQM caches pages in the DOM/memory so when you navigate back from two.html to one.html, pageinit won't fire (it's already initialized)
pageshow fires everytime a page is shown, this is what you need to be looking for when you navigate back from two.html to one.html
Together you can pull off a lot of clean code, use pageinit for initializing, configuration etc and update your DOM to the initial state. If you have dynamic data on the page that may change between views, handle it in pageshow
Here's a good design for larger websites that we use in a production environment:
bind a live event to all pages/dialogs pageinit and pageshow events in some include that is on every page:
$(document).on('pageinit pageshow', 'div:jqmData(role="page"), div:jqmData(role="dialog")', function(event){
I reference each page with a name: Now no matter what entry point a user lands on your site, all the handlers for all the pages are loaded. As you may already know, when you navigate to a page, it only pulls in Try not to use blanket selectors in your jQuery, e.g. The drawback is that all your js for your entire site is loaded on the first page the user reaches, but minified even a large site is smaller than jQuery or jQM so this shouldn't be a concern. But if your site really is large I suppose you could look into RequireJS. An advantage is you are no longer loading all your JS for each page through AJAX each time the user navigates to a new page. If all your JS is available on entry, you can now put debugger statements and debug much more easily! within the div[data-role="page"] - ignoring any JS in the , placing separate JS on each page is a mess and should be avoided in any large site I believe$('div.myClass') since this will search all of your DOM which may have more than one jQM page in it. Luckily in the live event handler for pageinit/pageshow mentioned above, this refers to the current page. So do all DOM searches within it, e.g. $(this).find('div.myClass') this ensures you are only grabbing elements within the current page. (of course this isn't a concern for ids). Note in the pageshow event you can also use $.mobile.activePage, but this isn't available in the pageinit, so I don't use it for consistency
I eventually had too much code, so I built a handler object where each page's js is included in a separate js file and can register handlers with the live event