Skip to content
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

Closed
andy1786 opened this issue Feb 28, 2019 · 5 comments
Closed

Page jumping on top while scroll on media gallery product page #21507

andy1786 opened this issue Feb 28, 2019 · 5 comments
Labels
Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed

Comments

@andy1786
Copy link

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.

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Feb 28, 2019
@magento-engcom-team
Copy link
Contributor

Hi @andy1786. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

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:

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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?

  • yes
  • no

@ghost ghost self-assigned this Feb 28, 2019
@magento-engcom-team
Copy link
Contributor

Hi @engcom-backlog-nazar. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • Next steps are available in case you are a member of Community Maintainers.

  • 6. Add label Issue: Confirmed once verification is complete.

  • 7. Make sure that automatic system confirms that report has been added to the backlog.

@ghost
Copy link

ghost commented Mar 1, 2019

Hi @andy1786 thank you for you report, this issue has already fixed in 2.3-develop branch #7906

@ghost ghost closed this as completed Mar 1, 2019
@Ctucker9233
Copy link

@magento-engcom-team Shouldn't this stay open until it's backported to 2.2? It seems a lot of bug fixes get missed.

@Ctucker9233 Ctucker9233 reopened this Mar 30, 2019
@ghost ghost removed their assignment Mar 30, 2019
@ghost
Copy link

ghost commented Apr 1, 2019

Hi @Ctucker9233 backport already here -> #22078 thank you for collaboration 👍

@ghost ghost closed this as completed Apr 1, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed
Projects
None yet
Development

No branches or pull requests

3 participants