microsoft / microsoft/microsoft-ui-xaml
InputNonClientPointerSource.GetForWindowId(AppWindow.Id) window resizing events not fired most of the time
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 8.4k
- Forks
- 942
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 105
Description
Describe the bug
I assume that InputNonClientPointerSource.GetForWindowId(AppWindow.Id) window resizing events such as EnteredMoveSize are meant to fire when resizing the window. However, these never seem to fire when resizing the window from the bottom or sides, and only occasionally from the top/top corners. It seems maybe the mouse has to be over the title bar for these events to fire. I would expect them to fire reliably when the window is resized, otherwise what is the point in them?
Steps to reproduce the bug
Add an event handler for InputNonClientPointerSource.GetForWindowId(AppWindow.Id).EnteredMoveSize then resize the window from the bottom or sides and observe it is not called.
Expected behavior
Resize events should be called reliably. IMO the WindowRectChanged event should also be called when the window is maximized etc (the docs say it corresponds to WM_WINDOWPOSCHANGED.
Screenshots
No response
NuGet package version
2.1
Packaging type
Packaged (MSIX)
Windows version
Windows 11 version 24H2 LTSC (26100, June Update)
IDE
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with an EnteredMoveSize handler on InputNonClientPointerSource.GetForWindowId(AppWindow.Id), resizing from the bottom, sides, and top corners. Trace the implementation of the non-client pointer events and WindowRectChanged behavior; done means resize and maximize operations reliably produce the documented events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100