-
Notifications
You must be signed in to change notification settings - Fork 706
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
Unexpected "InputSiteWindowClass" window appears in WinUI 3 app #10319
Comments
It is not a bug, it is created by Microsoft.UI.Input when a new window is created |
@castorix thanks for the feedback,the newly created "inputsitewindow" is greyed out in the hierarchy. And do you have any idea on this ? Because I checkedwith spy++ as well, any solution to make it visible? Or how to make it visible?thanks in advance . |
There are many non-visible windows used throughout the OS and its apps. Is it causing problems for you? |
@riverar ,Hi, my goal is to detect objects inside the application and use features like Object Spy in TestComplete. However, since this new window is introduced and greyed out, I cannot detect any objects within it. This issue occurs with all apps built using the WinUI3 framework. Is there any solution to make this window visible or bypass it? I am struggling to find the root cause, but I suspect the window is being greyed out by the application itself. Any thoughts or suggestions? |
It's an internal window, leave it alone? Why do you want to interact with it? |
There are objects under this window and this window is blocking me to detect those objects (need help ), any solution to make it visible or bypass this? and can you confirm that this window is from Microsoft.UI.Input this is the image of a working app where i am able to detect the underneath objects. |
It is greyed because WS_VISIBLE is not set
with :
|
@castorix Thanks ! it worked but the UIA tree is still greyed out, no idea why. |
this is jus the sample app , as same as https://github.com/microsoft/WinUI-Gallery |
If I use Inspect, I don't get this hierarchy for a sample app (same as UI Automation interfaces) |
From my tests with Inspect, the children of "InputSiteWindowClass" window are just the XAML controls |
this is for the sample app https://github.com/microsoft/WinUI-Gallery |
Describe the bug
I am experiencing an issue in my WinUI 3 application where an unexpected window with the class name InputSiteWindowClass appears, even though I am only initializing the main Window. This window is not explicitly created or referenced in my code, and it seems to be related to internal framework behavior, possibly related to input handling or focus management.
This issue doesn't occur in a similar app built using the same version of WinUI 3, which makes me believe it could be a bug related to how the framework handles certain window classes.
Steps to reproduce the bug
Create a basic WinUI 3 app (or use the sample app from GitHub).
Launch the app and inspect the UI hierarchy using Inspect.exe or Spy++.
Observe that an unexpected window with the class name InputSiteWindowClass appears, which is not explicitly instantiated in the code.
Expected behavior
Only the main Window should appear with the specified content. The InputSiteWindowClass should not be instantiated unless it is a part of the framework’s internal handling of input, which should be transparent to the user.
Screenshots
NuGet package version
WinUI 3 - Windows App SDK 1.6.3: 1.6.241114003
Windows version
Windows 11 (24H2): Build 26100
Additional context
The unexpected window is detected by Testing Tool and appears as a greyed-out object.
Tried debugging the code and checking for window creation in OnLaunched, but no explicit reference to InputSiteWindowClass is found.
Similar behavior is observed in a fresh WinUI 3 app that follows the same structure, but not in another app built with WinUI 3.
Other tools like Inspect.exe and Spy++ also show this window in the UI tree.
The text was updated successfully, but these errors were encountered: