SharePoint page autoscrolls to the top - specific behaviour

Copper Contributor

Hi all,


One of my colleagues came accross a rather strange bug in SharePoint sites. I have investegated it and think it is a bug that arose when updating to the newest Chrome version 120.0.6099.72.

 

This are my steps to reproduce. In order to reproduce I have disabled all my Chrome Plugins/extensions.

1. Create a new page on a SharePoint site with a lot of content (so that when scrolling, the menu gets smaller in height)

D_Rosenbaum_Linguatech_0-1702993598990.png

2. There must be at least 2 menu items available that are expandable. If they are not yet there, two items could be created with the  When not already there, add them.
3. Reload the newly created page
4. Click on the page and scroll down, at least untill the top menu gets smaller in height. Clicking on the page is very important.

D_Rosenbaum_Linguatech_1-1702993627232.png

 

 

5. Mousehover over the first menu

D_Rosenbaum_Linguatech_2-1702993643320.png

 

6. Mousehover over the second menu

7. Notice that the page automatically scrolls to the top of the page.

 

Could someone please look into this?

Kind regards,
Dennis Rosenbaum

 

2 Replies

@D_Rosenbaum_Linguatech 

Appreciate your keen observation on the auto-scroll glitch – definitely a bit of a head-scratcher. I replicated your steps, and indeed, the page zooms up on Chrome Version 120.

 

This seems to tie back to a recent Chrome update impacting SharePoint suite bar links, messing with the smooth sailing. My first recommendation is to report about this bug here:

 

https://bugs.chromium.org/p/chromium/issues/list

 

and here: https://learn.microsoft.com/en-us/sharepoint/dev/support-feedback

 

Getting this visibility across channels usually nudges things in the right direction. As a workaround, temporarily sticking to a previous Chrome release seems to sidestep the scrolling hiccup. But logging it officially is our best bet for a solid fix.

@BarryGoblon Thank you very much for pointing me in the right direction.

I have created a Chromium bug and a Microsoft Support ticket through our Microsoft 365 account.

 

Now we'll wait.