What happened?
We are using WebView2 in composition mode. When the host machine is accessed through Remote Desktop, the IME candidate window/composition UI appears at the wrong position inside WebView2 text inputs.
After disconnecting the Remote Desktop session, the IME position becomes correct again on the local machine.
What we also observed:
- The issue happens only when WebView2 is running in composition mode.
- Recreating the WebView2 control during the remote session does not fix the IME position.
- After leaving the remote session, the IME coordinates become correct again.
Reload() can trigger a new navigation correctly in our other test case, so this IME issue appears unrelated to simple navigation state.
This makes us suspect the IME popup/candidate window position is not recalculated correctly after session/display environment changes caused by Remote Desktop.
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
Please fill in exact version.
SDK Version
Please fill in exact SDK version.
Framework
Win32
Operating System
Windows 10 or Windows 11
OS Version
Please fill in exact OS build.
Repro steps
- Create a Win32 app hosting WebView2 in composition mode.
- Navigate to a page with a text input or textarea.
- Connect to the machine using Remote Desktop.
- Focus the text input and activate an IME.
- Observe that the IME candidate window/composition UI appears at the wrong screen position.
- Disconnect Remote Desktop and return to the local session.
- Focus the same input again.
- Observe that the IME position is correct again.
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version.
Regression
Don't know
Last working version (if regression)
No response
Additional context
We tried recreating the WebView2 instance during the remote session, but the IME position was still wrong.
We suspect this may be related to Remote Desktop session changes, DPI / rasterization scale changes, or parent window position updates not fully refreshing IME popup coordinates in composition mode.
It would be helpful to know whether there is any supported way to force WebView2 to recompute IME candidate window coordinates after remote session changes.
What happened?
We are using WebView2 in composition mode. When the host machine is accessed through Remote Desktop, the IME candidate window/composition UI appears at the wrong position inside WebView2 text inputs.
After disconnecting the Remote Desktop session, the IME position becomes correct again on the local machine.
What we also observed:
Reload()can trigger a new navigation correctly in our other test case, so this IME issue appears unrelated to simple navigation state.This makes us suspect the IME popup/candidate window position is not recalculated correctly after session/display environment changes caused by Remote Desktop.
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
Please fill in exact version.
SDK Version
Please fill in exact SDK version.
Framework
Win32
Operating System
Windows 10 or Windows 11
OS Version
Please fill in exact OS build.
Repro steps
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version.
Regression
Don't know
Last working version (if regression)
No response
Additional context
We tried recreating the WebView2 instance during the remote session, but the IME position was still wrong.
We suspect this may be related to Remote Desktop session changes, DPI / rasterization scale changes, or parent window position updates not fully refreshing IME popup coordinates in composition mode.
It would be helpful to know whether there is any supported way to force WebView2 to recompute IME candidate window coordinates after remote session changes.