[Windows] Verify: events, input and icon reports from window_manager
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- flutter
- Domain
- desktop, operating-systems, testing-qa
Research direction
Build a Flutter app using the Window API and reproduce each linked window_manager report against nativeapi 0.6.0. Start with the relevant nativeapi window behavior and check Application::SetIcon with a path inside flutter_assets. For each report, either verify and fix the behavior or record that it no longer occurs, then tick off the checklist item.
Written by the indexing model from the issue text.
Description
These were reported against window_manager 0.5.x, whose platform code is gone: window_manager 0.6.0 is rebuilt on nativeapi. None of them has been checked against nativeapi yet. Each needs a reproduction with nativeapi (a Flutter app on the Window API), then a fix or a note that it no longer happens. Tick them off here as they're checked.
- leanflutter/window_manager#207: resize event not fired for snapping (Win+Arrow, Windows 11 snap layouts, double-click on the title bar)
- leanflutter/window_manager#294: blur event reported when a minimized window is restored, instead of focus
- leanflutter/window_manager#480: first Enter/Escape key swallowed after hiding or minimizing from code and showing again
- leanflutter/window_manager#511: maximize() doesn't work while the mouse is captured (called from onDoubleTapDown)
- leanflutter/window_manager#245: moving between monitors with different scale factors changes the window size and causes overflow
- leanflutter/window_manager#534: setIcon() has no effect (Windows 11); check
Application::SetIconwith a path inside flutter_assets
- Dominant language
- C++
- Stars
- 34
- Forks
- 7
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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.
More from libnativeapi/nativeapi
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
libnativeapi/nativeapi#81 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
libnativeapi/nativeapi#80 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
libnativeapi/nativeapi#79 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
libnativeapi/nativeapi#77 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
libnativeapi/nativeapi#76 ·
All issues in libnativeapi/nativeapi
Similar issues
-
AuTest Bug Tests
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/trafficserver#13714 ·
-
bug build
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
facebookincubator/velox#19143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
tenstorrent/tt-metal#57393 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
objectionary/eo-graphs#74 ·