MicrosoftEdge / MicrosoftEdge/WebView2Feedback

Navigation sometimes ignores ordering

Open
#2,336 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description
We provide a list of documents users can browse - which we translate into a navigation to said document. Sometimes they will report that the selected document is not what is shown in the browser. In those cases we got the following log statements:

14:52:34,001 [Main] WebView System navigation (for type 'NavigationStarting (id: 421)' and address 'xxxDoc1') - [WebView hash '47801319']
14:52:34,052 [Main] WebView System navigation (for type 'NavigationStarting (id: 422)' and address 'xxxDoc2') - [WebView hash '47801319']
14:52:34,054 [Main] WebView Navigation to id: 422 ended as failure with status ConnectionAborted - [WebView hash '47801319']
14:52:34,084 [Main] WebView Navigation to id: 421 ended as succes - [WebView hash '47801319']

The problem seems to be that when two nagivations occur very close together we are not guaranteed that the latest navigation (id 422) will win the race.

Version
SDK: 1.0.1108.44
Runtime: Evergreen 100.0.1185.29
Framework: WPF
OS: Windows 10 Pro - OS Build: 19044.1586

Repro Steps
I have not been able to effectively reproduce this, but it only seems to occur when there is less than a second between navigations.

AB#38990422

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.

Research direction

Start by tracing the WebView2 navigation lifecycle around the NavigationStarting and completion events described in the logs. Reproduce or instrument two navigations occurring less than a second apart, then verify that the later navigation remains the displayed document rather than being replaced by the earlier one.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.