[Windows] Verify: hidden title bar frame, border and maximize details
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cpp, flutter
- Domain
- desktop, operating-systems, testing-qa
Research direction
Start by reproducing each listed window_manager case in a Flutter app using the Window API against nativeapi. Read the reworked Windows hidden-title-bar implementation, then verify each item and either fix the behavior or record that it no longer occurs.
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.
The Windows hidden-title-bar implementation has been reworked in nativeapi (WS_CAPTION kept, top-edge hit testing, DWM frame extent), so several of these may already be fixed.
- leanflutter/window_manager#547: top border missing with TitleBarStyle.hidden (Windows 10 especially)
- leanflutter/window_manager#554: maximize covers the taskbar with a hidden title bar
- leanflutter/window_manager#450: 1-pixel gap to the taskbar when a frameless window is maximized
- leanflutter/window_manager#378: extra padding in full screen with a hidden title bar
- leanflutter/window_manager#397: title bar flashes when leaving full screen with a hidden title bar
- leanflutter/window_manager#576: Windows 11 caption buttons missing or flickering, title disappears (with a transparent background colour)
- 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#78 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
libnativeapi/nativeapi#77 ·
All issues in libnativeapi/nativeapi
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
objectionary/eo-graphs#74 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 88/100
QuantStack/git2cpp#187 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100