We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hey Matt, here's an interesting one for you:
In the page init I have:
$("#settingsPage").on("swiperight", function () { goBack();; });
On the page I have:
<input type="range" min="0" max="200" step="1" value="25">
When I move the slider to the right from the default of 25 to 100, the swiperight gets invoked.
I tried this:
$("#settingsPage not:input").on("swiperight", function () { goBack(); });
and this: $("#settingsPage").not(".no-swipe").on("swiperight", function () { app.views.main.router.back('/account/', {force: 'true', ignoreCache: true}); });
with this html:
<input class="no-swipe" type="range" min="0" max="200" step="1" value="25">
I also tried with the class="noSwipe" as referenced here
Any suggestions on how to have a page swipe handler that works with the range slider? (BTW, I'm using this with Framework7 ver 5.x)
The text was updated successfully, but these errors were encountered:
Never mind. I added the elements to the exclude list and that worked.
Sorry, something went wrong.
No branches or pull requests
Hey Matt, here's an interesting one for you:
In the page init I have:
On the page I have:
When I move the slider to the right from the default of 25 to 100, the swiperight gets invoked.
I tried this:
and this:
$("#settingsPage").not(".no-swipe").on("swiperight", function () {
app.views.main.router.back('/account/', {force: 'true', ignoreCache: true});
});
with this html:
I also tried with the class="noSwipe" as referenced here
Any suggestions on how to have a page swipe handler that works with the range slider?
(BTW, I'm using this with Framework7 ver 5.x)
The text was updated successfully, but these errors were encountered: