MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: Scroll Position Resets on Back Navigation in WebView2

Open
#5,385 1 comment 0 reactions 1 assignee View on GitHub

@prija-microsoft is already working on this.

Since Oct 23, 2025.

bug
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

I’m using WebView2 in my application and noticed that scroll position is not preserved after navigating back.

I have a list of around 100 links on a single page. When I scroll down and click a link near the middle or bottom, I navigate to a new page. But when I press the back button, the scroll position resets to the top of the page.

This behavior does not occur in regular browsers like Google Chrome, where the scroll position is preserved after back navigation.

Importance

Blocking. My app's basic functions are not working due to this issue.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

No response

SDK Version

No response

Framework

Other

Operating System

Windows 11

OS Version

No response

Repro steps

Scroll Position Resets on Back Navigation in WebView2
I’m using WebView2 in my application and noticed that scroll position is not preserved after navigating back.

I have a list of around 100 links on a single page. When I scroll down and click a link near the middle or bottom, I navigate to a new page. But when I press the back button, the scroll position resets to the top of the page.

This behavior does not occur in regular browsers like Google Chrome, where the scroll position is preserved after back navigation.

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

No, this never worked

Last working version (if regression)

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.