-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Problem/Bug]: webview2 runtime 121.0.2277.83 is preventing users from typing in text fields when SetWindowDisplayAffinity is enabled #4325
Comments
@cgits14 Sorry that you are hitting it. We have found root cause and in the process of fixing the issue. It seems that mouse input is what's actually broken - but keyboard can still be used to tab to the content and insert the characters - could you please check if it is reasonable workaround for your app? Also how bad is the impact on your side? |
@vbryh-msft That is good news. This hit us pretty hard, we had to resort to overriding the option for those on the latest version of the runtime, fortunately it only seems about 25% of our users are on the latest at the moment. My concern was this was going to get worse as we head into the weekend. Do you have an ETA? This workaround is good to know, but I don’t think it is any better than our current one. |
We paused roll-out of stable for now. The ETA for the fix is February 1 + 60 hours to reach 100% of users. |
Hi, we have got some customers who already got version 121. Is there a way to remove this update? |
See this page: https://learn.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution Depending on where it's installed you go here (on 64 bit Windows): %localappdata% and set pv to 0.0.0.0 make sure nothing is running that uses webview 2 and install the older version. |
@vbryh-msft Can you comment on when we will see a patch released for this? |
@mackid1993 it is planned for today - we are in PST time zone. Will update at the evening. As a follow-up of this issue - please set-up testing/self hosting of your app on our prerelease channels and report the issues before they reach Stable and your end users. |
121.0.2277.98 version has a fix and is being released. |
@vbryh-msft thank you. I can confirm we are good now. |
@Musicstave you issues does not look related to what was discussed in this thread and to webveiw2. If it reproes in Edge browser only, please report it to Edge -> Help and Feedback -> Send feedback. If it reproes across different browsers - report it to Bing. That way you will have correct people look into it. Thanks |
What happened?
Starting yesterday with webview2 runtime 121.0.2277.83 we started receiving reports from users in the field where they could no longer type in text boxes on web forms. This issue goes away when we do not set the SetWindowDisplayAffinity setting, but when we set it the users cannot enter any text and the boxes appear disabled. We need this setting enabled for security and is impacting all of our users.
The text boxes I am seeing this behavior on are user name and password entries. It’s possible there could be others, but we can’t get further. I feel like this might be an important distinction.
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime), Prerelease (Edge Canary/Dev/Beta)
Runtime Version
121.0.2277.83
SDK Version
No response
Framework
Win32
Operating System
Windows 10, Windows 11
OS Version
Any
Repro steps
Enable SetWindowDisplayAffinity to WDA_MONITOR. Load a web form with text input controls.
Repros in Edge Browser
Not Applicable
Regression
Regression in newer Runtime
Last working version (if regression)
No response
AB#48696537
The text was updated successfully, but these errors were encountered: