rust-windowing / rust-windowing/winit
Minizing the window sends a resize event with 160x28 on Windows
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 1.3k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 9
Description
Minizing the window sends a resize event with 160x28 on Windows (at least on my machine). This causes an unfortunate event in alacritty on Windows, where a strange behavior in conpty decides to delete scrollback history (https://github.com/alacritty/alacritty/issues/7074)
While this is technically not winit's problem, I wonder where the very particular resolution comes from. Is it directly from VM_SIZE? Older versions of winit used to send 0x0. The information would be useful to inserting platform-specific workarounds to alacritty so that at least some of the weirdness in conpty could be avoided.
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 tracing the Windows minimize and resize-event handling, especially the path associated with VM_SIZE. Determine where the 160x28 dimensions originate and compare that behavior with older versions that emitted 0x0; done means documenting the source clearly enough for alacritty to apply a platform-specific workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100