History API - Scroll restoration | Blog | Chrome for Developers

Using the History API to manage your URLs is awesome and, as it happens, a crucial feature of good web apps. One of its downsides, however, is that scroll positions are stored and then, more importantly, restored whenever you traverse the history. This often means unsightly jumps as the scroll position changes automatically, and especially so if your app does transitions, or changes the contents o

[reboot_in]

“history.scrollRestoration. It takes two string values: auto, which keeps everything as it is today (and is its default value), and manual, which means that you as the developer will take ownership of any scroll changes that may be required when a user traverses the app's history. If you need to,

[eedamame]

“history.scrollRestoration”

[fushimik]

ブラウザの戻るボタンで、スクロール位置も元に戻す。

[UDONCHAN]

スクロール位置まで記憶

[efcl]

history.pushStateでスクロール量も記憶する

[masakiplus]

Using the History API to manage your URLs is awesome and, as it happens, a crucial feature of good web apps. One of its downsides, however, is that scroll positions are stored and then, more importantly, restored whenever you traverse the history.