In my JQuery Mobile app, I'm manually calling history.replaceState when loading a page as the result of a GET or a POST. I'm doing this so that the URL query parameters match the data being returned, to create a bookmarkable results page. This seems to work OK when I'm returning from a POST, but when I attempt to do a GET by entering a URL in the browser's location bar, I often end up on a different page than intended, not the parameters I put into the location bar. I've tried issuing the history.replaceState on pagechange and on pageshow. If I remove the history.replaceState, I don't have the problem when I attempt to do a GET by entering a URL in the browser's location bar.
Is manually calling history.replaceState supposed to work with JQuery Mobile? Is there a recommend ready event to use to fire it?
Can Cycle2 be configured to emulate the type of instant horizontal scroll behavior that's available with iScroll or iosslider? In other words, can the swipe action be made to move the slide as though it's stuck to one's thumb?
I'm working on a web app that uses JQuery Mobile 1.3.1 and Cycle2. An Android tester for this app is having a swipe issue for the Cycle2 carousels on their Samsung Galaxy S4.
"As for bugs on Cycle2, the main issue has been swipe support on Android. Swiping seems to work fine on the iPhone, but on Android devices swipe detection is not consistent and on the Cycle2 demo page the swipe scroll didn’t work at all."
With JQM 1.3.0 RC1, and also "the latest", when I do a first visit or hard refresh on a page, and enter data, the form data being submitted will not only contain the correct fields and values it's supposed to, but it will also contain an extra empty copy of the fields which is interfering with my model binding. Like this in desktop Windows 7 Chrome developer tools Header/Form Data results:
If my web app returns results to the originating page in the browser following this bad postback, and then I post again, the post works correctly (only single copies of the form data are being sent). The problem only happens either when first visiting a page or after I manually reload the page with the browser reload button.
This doesn't happen with JQM 1.2.0. Can anyone take a look at their browser post output and replicate this? I'm new to JQM so maybe it's me.