Steps to reproduce
- Open a webpage, for example, the issue can be recreated with “https://openwhyd.org/u/50ae222c7e91c862b2a8d795/playlist/0”
- Scroll down.
- After some usage (no input done on the specific tab) and returning to the top, the website is positioned at the top again.
Although perhaps a separate issue, this behavior can also repeatedly be triggered by searching on the page (ctrl-f), at which point undesirably the page jumps to the top.
Comments and activity
Apologies. I meant “After some usage (no input done on the specific tab) and returning to the TAB, the website is positioned at the top again.”
- Microsoft Edge Team
Changed Assigned To to “Ibrahim O.”
Changed Assigned To to “Rick J.”
The same behavior happens in Chrome when resizing the window (also occurs in Edge). I believe the root cause is the website itself (openwhyd.org).
Interestingly, it does not occur in Chrome when searching. Perhaps a different way this is handled between browsers.
Not only Edge but all of the systems that accept “refresh” will incorporate the refresh. Then scatter the information in the refresh throughout the page causing the page to jump and the reader to loose their place on the page. The reader then must, in mid-sentence look for the place they were reading and continue until the next refresh and start the same process all over again. Similar to “whack a mole.”
If the refresh could simply be placed at the bottom of the page and not cause the page to bounce around while in use, It would make Edge much more user friendly and less of a pain in in used food chute.
- Microsoft Edge Team
Changed Assigned To from “Rick J.” to “Matt R.”
Changed Status to “By design”
You are correct that this behavior is due to the website’s code, and so this issue is unfortunately by design. Openwhyd has a resize handler that forces the scroll offset to 0 on every resize in both Edge and Chrome:
// from whyd.js
document.body.scrollTop = document.documentElement.scrollTop = 0;
Since the find on page UI is a full width bar in Edge, opening/closing the UI triggers a viewport resize and therefore the logic above. Whereas Chrome uses an overlay UI that does not resize the viewport.
Jan C., it sounds like the symptom you are describing is somewhat different. Since this issue is referring to the specific behavior on openwhyd.org jumping to the top, it would be great if you could file a separate issue for the site and symptom you are observing.