The issue is an autoscroll to the top of the page when accessing search, user, or hamburger comboboxes in Chrome, but only when the combobox detaches from the right side of the screen, typically around 1350 pixels. pettro provided screenshots and confirmed the issue occurs on community.home-assistant.io and in safe mode.
codinghorror initially suspected a CSS theming and layout issue but was unable to reproduce it. pettro confirmed it happens on try.discourse.org as well.
The issue was later confirmed by Moin and thanasis, who also experienced it in Chrome but not Firefox.
Johani discovered the root cause was a bug related to CSS sticky and provided a link to a pull request that fixed the issue on Meta. Johani further explained that the bug only occurs when the “Experimental Web Platform features” flag is enabled in Chrome and provided instructions to disable it.
Using community.home-assistant.io w/ chrome Version 95.0.4638.54 (Official Build) (64-bit). Having an odd issue, only present on my home desktop. Work desktop appears to be fine, however I don’t know the current chrome version.
This issue:
Clicking on search, hamburger (3 vertical lines), or your user icon, the page auto scrolls to the top of the current scrollbar instead of exposing the combobox.
The issue only occurs when the combobox detaches from the right side of the screen so that there would be a gap between the combobox and the vertical scroll bar. This appears to be somewhere around 1350 pixels in x including the vertical scroll bar.
EDIT: The only way it will appear when the combobox is detached is when you’re at the top of the page (Post 1):
I am having trouble reproducing this, what are the specific steps? I have a super wide browser, I am scrolled down in this topic and I am clicking on the avatar and it isn’t scrolling to top?
We had someone reporting the same.
Version 95.0.4638.54 (Offizieller Build) (64-Bit)
He also tried to use the keyboard shortcuts, but the problem was the same.
I’m willing to try anything and I’ve been developing for years now. This bug is annoying the crap out of me, any direction/link/whatever towards finding the root cause of this issue would be welcomed seeing that you can’t reproduce it.
I read a little bit more about this and managed to track down the issue. This bug - and a few other bugs relating to CSS sticky - will only occur if you have
Experimental Web Platform features
enabled in Chrome flags. This explains why only some people were getting it even though it’s the same version of Chrome.
If you’re seeing this issue. Make sure that it’s disabled here.
