Some settings pages (mostly those with routes with a depth greater than that of the main page) use a horizontally sliding animation to transition between their parent and child route pages. For example, this may include the cookies page (chrome:settings/content > Cookies and vice versa), and its child pages as well.

For long pages that require a scrollbar, navigating to a child page with this sliding animation makes the long page snap back up to the top of the page before executing the slide animation. Upon pressing the back button on the child page, the user's original scroll position on the long page is not retained. An example of this can be seen in chrome://settings/siteData page, which contains a long list of cookies, and navigating to its child pages (chrome://settings/cookies/detail?site=example.com).

Investigate fixing this by transforming child pages' y-position to the scroll position of the parent page on navigation and vice versa.