Scrolling issue in backend pages | bouncing up and down

[ioweb-gr]

Preconditions (*)

1. Magento 2.3.x
2. A backend edit page that fits the window height exactly and has buttons on top for actions like "Save" "Delete".

Summary (*)

This is very hard to reproduce on an environment but I've seen it happening in category edit page, product edit page and a lot of other module pages in all versions of Magento from 2.2.4 to 2.3.1.
There is probably a script that's preventing users from scrolling up when the whole document form can be seen in the current window so when you scroll up you're returned to the same point you were in the screen although the scrollbar still exists.
In rare occassions, when the sticky header appears, the size of the document of the document is altered and it causing an infinite bouncing effect.
Since it's very hard to describe I decided to capture it on a video and attaching it here. If someone can help me out on how to replicate it every time I would appreciate it so that I can write detailed steps.

Steps to reproduce (*)

1. On a clean firefox install right click on top window bar and enable Menu bar and Bookmarks toolbar. Firefox normal not developer preview.
2. Open responsive design tool
3. Set dimensions to 1920x926px
4. Windows taskbar on the bottom
5. Navigate to catalog -> category
6. Open the first category
7. Expand schedule design update
8. Scroll to the bottom and then up.

Expected result (*)

1. User is able to scroll up and down normally

Actual result (*)

1. In one occassion I'm unable to scroll up and returned to my original scroll point.
   
   The problem stops immediately when I expand one tab.

2. In worst case scenario the page bounces until I have to reload the page.
   

[m2-assistant]

Hi @ioweb-gr. 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.

@ioweb-gr do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[ioweb-gr]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @ioweb-gr. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @ioweb-gr, here is your Magento instance.
Admin access: https://i-22392-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[ioweb-gr]

Replicated on 2.3-develop instance.

Steps I tried:

1. Go to edit category
2. Expand the Schedule Design Update section only and keep the other ones closed.
3. Scroll to bottom
4. Try to click the "up arrow" in scrollbar and notice the bounce.

Maybe it helps but in my case the html height was 916px and body height 1107.53px

[m2-assistant]

Hi @shikhamis11. 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).

  Details

  If 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

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

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

[shikhamis11]

Hello @ioweb-gr
Thank you for your report can you please also add details of your browser and os so that I could check on that.

[ioweb-gr]

Yes of course. I'm on Windows 10 x64 and I've seen this happen on Firefox 67 and google chrome Version 73.0.3683.103 (Official Build) (64-bit)

.

[shikhamis11]

hello @ioweb-gr . I tried on windows and linux as well . I am not able to reproduce this issue .. let me check if someone can reproduce this issue .

[m2-assistant]

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).

  Details

  If 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

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

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

[ioweb-gr]

Hi, yes indeed it's very hard to reproduce because it depends on the resolution of the window and the inner contents of the page. I haven't been able to find the exact dimensions for both to replicate it consistently but it definitely exists. If I can do anything to help you replicate it please let me know.

[m2-assistant]

Hi @ajijshekh123. 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).

  Details

  If 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

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

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

[ajijshekh123]

Can you please give me Magento 2.2.4 Version?

[ajijshekh123]

Give me @magento-engcom-team give me 2.3-develop instance?

[magento-engcom-team]

Hi @ajijshekh123. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @ajijshekh123, here is your Magento instance.
Admin access: https://i-22392-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[ajijshekh123]

Give me @magento-engcom-team give me 2.2.4-develop instance?

[magento-engcom-team]

Hi @ajijshekh123. Thank you for your request. I'm working on Magento 2.2.4-develop instance for you

[ajijshekh123]

Give me @magento-engcom-team give me 2.2.4-develop instance?

[magento-engcom-team]

Hi @ajijshekh123. Thank you for your request. I'm working on Magento 2.2.4-develop instance for you

[ajijshekh123]

Please give me @magento-engcom-team give me 2.2.4-develop instance?

[magento-engcom-team]

Hi @ajijshekh123. Thank you for your request. I'm working on Magento 2.2.4-develop instance for you

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-11927 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[github-jira-sync-bot]

❌ Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-11927

[github-jira-sync-bot]

❌ Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-11927