[Linux] Verify: reports carried over from window_manager
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cpp, flutter, linux
- Domain
- desktop, operating-systems, testing
Research direction
Start with a Flutter app using the Window API and reproduce the nine linked window_manager reports on Linux, including the listed desktop environments and embedding case. Check off each report after confirming it, fixing it, or recording 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.
- leanflutter/window_manager#167: full screen doesn't work (Arch Linux)
- leanflutter/window_manager#535: in full screen, each hide/show shifts the window further off-screen
- leanflutter/window_manager#179: transparent background colour renders black (Arch, KDE Wayland)
- leanflutter/window_manager#370: a longer title set before showing is ellipsized to the original length until resize
- leanflutter/window_manager#411: setSize has no effect (Hyprland, Ubuntu 22.04)
- leanflutter/window_manager#427: onWindowResize fires in an endless loop
- leanflutter/window_manager#497: window visibly repositions on start
- leanflutter/window_manager#519: black window when the app runs as a GTK_PLUG (embedded in another app)
- leanflutter/window_manager#561: title bar glitches with min/max size or setResizable (KDE Plasma 6 Wayland, NVIDIA)
- 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 45/100
libnativeapi/nativeapi#78 ·
-
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 ·