The modules page has several auto-scrolls that happen when it reloads. It loads all of the modules, it scrolls to where you last were, it scrolls to the top of the page, and it scrolls to the top of the first open module. The sequence might depend on what steps caused the page to reload. When editing content, it would be helpful to reload at the place you are currently editing, but you might end up at the top of the page. Students working through a module, might also find it to be useful to pick up where they left off, and instead become distracted by other content back at the top of the page. When first returning to the modules page, from a page accessed without a module link, it might be helpful to start at the top of the first open module, since you have not necessarily aimed at the most recently accessed part of the page. If you respond to your needs while a long module page is loading, you might get part way to your destination before the auto-scroll returns you to somewhere else to start over.
Update the modules page to reload at the item that you are returning from, when the immediately previous page was accessed via a module item, or the update is a response to a drawer. When arriving at the modules page otherwise, begin at the first open module. If you scroll the page manually during the load-time, default to user control, instead of correcting to where the page is set to load. Also, provide a button to return users to the top of the page for occasions when that is needed, and make that button available to use even if the rest of the page is still loading.
