-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
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
Page jumping on top while scroll on media gallery product page #21507
Comments
Hi @andy1786. Thank you for your report.
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
For more details, please, review the Magento Contributor Assistant documentation. @andy1786 do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
|
Hi @engcom-backlog-nazar. Thank you for working on this issue.
|
@magento-engcom-team Shouldn't this stay open until it's backported to 2.2? It seems a lot of bug fixes get missed. |
Hi @Ctucker9233 backport already here -> #22078 thank you for collaboration 👍 |
Preconditions (*)
Problem is on Magento 2.2.6, product page with media gallery
Steps to reproduce (*)
When I am on product page on mobile and I swipe down then is automatically pushing me on the top of the page. It is scrolling for 50% of the page and then is scrolling up. If I swipe faster, then is getting the gallery out of the screen and there is no problem anymore.
This is only on Android phones and I could not reproduce it on iOS or browsers on desktop.
Expected result (*)
When I disable swipe from view.xml, then this should not happen anymore.
Actual result (*)
When I am on product page on mobile and I swipe down then is automatically pushing me on the top of the page. It is scrolling for 50% of the page and then is scrolling up. If I swipe faster, then is getting the gallery out of the screen and there is no problem anymore.
The text was updated successfully, but these errors were encountered: