microsoft
Regresssion: Composition drawing broken in multi-window app (worked in 1.5)
Describe the bug
The PointerOver test on controls fails intermittently in the first window after a second window is opened when built with WinAppSdk 1.6. The bug isn't evident 100% of the time, but in my set up it's > 50%. I haven't been able to reproduce this behaviour building against WinAppSdk 1.5.
Please see the video of the attached project running. You can see as the mouse is moved over the button on the first window, the PointerOver indication flashes then goes out, although the button isn't clicked (I changed the PointerOver brush to make it more obvious). You can still click on the button successfully even when the pointer over isn't shown.
Other controls exhibit the same fault. Trimming (or not) doesn't change the out come. Removing the mica background did make it more difficult to reproduce, but it may be a simple timing issue. I'm not sure if this is win app sdk or xaml bug.
https://github.com/user-attachments/assets/e9261c00-b052-487b-8318-abb27552ee19
Steps to reproduce the bug
- Build and run the attached project
- Click the "New Window..." button
- Switch back to the first window
- Move the mouse over the button to see the effect
Expected behavior
No response
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.6.1: 1.6.240923002
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response
Edit: Of course it's pointer over not mouse over. I've also made the repro project code a bit more robust, but didn't change it functionality.
The fault is easier to reproduce in my actual app, which has a more complex ui. Build the master branch if required. The video again demonstrates the fault. The colour picker palette entries animate using a scale transition that's triggered by a pointer entered event handler. That now fails as does hovering over the tab item header.
https://github.com/user-attachments/assets/eeaf82ae-9033-4ff0-964b-c3d475667563
Still reproducable on 1.7
Why am I not surprised? What a ridiculous state of affairs this is. It's not as if multi-window apps are an edge case.
With the new version of the WinUI Gallery app (2.6.0.0), I do not observe this issue. It uses the same version of the WinAppSDK as our app, where the issue is still present. I will check if the WinUI Gallery uses any other Windowing API for its AppWindow example, but perhaps someone from the Microsoft UI team could comment on this.
Please fix this. It still happens in 1.7.2 Many of our customers experience clicks/taps that do not register that might be related to PointerOver behavior: buttons hover are flickering in this situation.
@codendone I am tagging you, since you helped me out many times by raising awareness of issues. This issue is very easy to reproduce (see the ExctendsContentIntoTitleBar issue for steps) and causes much trouble.
Issues https://github.com/microsoft/microsoft-ui-xaml/issues/10357 / https://github.com/microsoft/microsoft-ui-xaml/issues/10067 / https://github.com/microsoft/microsoft-ui-xaml/issues/10529 and https://github.com/microsoft/microsoft-ui-xaml/issues/10572 seem to be related.
It would be good if the issues would be combined in the internal system at Microsoft so the issue gets the appropriate visibility/priority
In my case, removing ExtendsContentIntoTitleBar from child windows resolved the issue. There is no flickering after a child window is hidden or minimized.
Still not fixed in 1.7.3 Please fix asap. It is the top issue our (many!) customers see in WindowsAppSDK.
Seems fixed in 1.8.0 (stable) as indicated in the release notes. I can't reproduce the bug any more.