Repository navigation
WebView2 library downgrade - #329
Merged
Merged
Conversation
tomaszgolebiowski
approved these changes
Jul 28, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After updating
Microsoft.Web.WebView2to version1.0.3296.44some users have started reporting problems with the chat rendering (an empty Cody window).Looks like last update to
1.0.3351.48doesn't resolve the issue also, so downgrading to1.0.2592.51which is the latest good working version. Unfortunately it does not have fix for MicrosoftEdge/WebView2Feedback#286 (WebView2 is always on the top of the other controls).Users are reporting a blank Cody window, but looks like internally that the page is loaded, and when interacting with the control the cursor is changing and reacting to different page areas (e. g. buttons).
More context: https://sourcegraph.slack.com/archives/C073U3KE5DK/p1753121170575139
Probably related:
Test plan
Monitoring affected users after they will update the extension (no working repro steps at this moment).