MicrosoftEdge / MicrosoftEdge/WebView2Feedback
WebView2: navigating to second page causes remote messenger error
@champnic is already working on this.
Since Jan 22, 2021.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Description
Navigating the webview2 browser to a web page with host objects bound, making calls to window.chrome.webview.hostObjects, and then later navigating to another page seems to reprocess existing remote messenger responses, which then generates a host of javascript errors because the response has already been processed. This seems like a bug with webview2 or am I doing something wrong? Is there presently a workaround?
VM6:1 Assertion failed: no call detail for 98
_handleResponse @ VM6:1
(anonymous) @ VM6:1
(anonymous) @ VM7:1
(anonymous)
Version
SDK: 1.0.664.37
Runtime: 87.0.664.55
Framework: WinForms
OS: Win10
Repro Steps
1). Create webview2 instance and bind a hostObject.
2) Load URL
3) Make calls to hostObject via window.chrome.webview.hostObject
4) Navigate to new URL (google.com) via window.location = or reload the page.
5) Error is generated by in RemoteMessager class. Interface appears to be reprocessing already processed responses to hostObjects.
Screenshots
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.