Response title
This is preview!
JQM Behavior Issue - execution works the first time, crashes the second time around
in jQuery Mobile
•
11 years ago
Hey Developer Community,
I'm facing the weirdest behavior by JQM and am wondering if you guys may have an idea or thought on what it could be caused by. I'd really appreciate any help!
Here's my problem: I am developing a cross-platform mobile app using the Rhomobile framework. I have included JQM 1.0 properly and its working great (for the most part). Now, I have a navigation stack (Home -> Resultlist -> Detailview), when traveling down to the detailviews, JQM ajaxifies my links nicely and transitions are working smoothly. When I see my detailview and want to go back, I have a native back button in my Navbar on top of the screen. As its not part of the webview I execute the JS code thru my controller using the $.mobile.changePage('/app/Display/resultlist', { reverse:true, reloadPage:true }) command. That works great the first time. I get my resultlist shown and I'm happy. If I so choose to call the same detailview right after again, the click event is being executed (I added an alert on the event to see whats happening) but no query is logged on the server side?!
I first thought it could be a rhodes issue but disabling JQM causes the program to work nicely (except without transitions booo). Now, could it be that JQM somehow remembers already having called that page and thus trying to find it in some sort of browser cache (which might not exist in a rhomobile framework?) or why doesnt the second click cause the same query on the server side than the first one a minute before?
I"m presuming its a caching problem but I have no clue as to how to tackle it. I appreciate the smallest hint guys. Thanks so much!
I'm facing the weirdest behavior by JQM and am wondering if you guys may have an idea or thought on what it could be caused by. I'd really appreciate any help!
Here's my problem: I am developing a cross-platform mobile app using the Rhomobile framework. I have included JQM 1.0 properly and its working great (for the most part). Now, I have a navigation stack (Home -> Resultlist -> Detailview), when traveling down to the detailviews, JQM ajaxifies my links nicely and transitions are working smoothly. When I see my detailview and want to go back, I have a native back button in my Navbar on top of the screen. As its not part of the webview I execute the JS code thru my controller using the $.mobile.changePage('/app/Display/resultlist', { reverse:true, reloadPage:true }) command. That works great the first time. I get my resultlist shown and I'm happy. If I so choose to call the same detailview right after again, the click event is being executed (I added an alert on the event to see whats happening) but no query is logged on the server side?!
I first thought it could be a rhodes issue but disabling JQM causes the program to work nicely (except without transitions booo). Now, could it be that JQM somehow remembers already having called that page and thus trying to find it in some sort of browser cache (which might not exist in a rhomobile framework?) or why doesnt the second click cause the same query on the server side than the first one a minute before?
I"m presuming its a caching problem but I have no clue as to how to tackle it. I appreciate the smallest hint guys. Thanks so much!
1