[macOS] Verify: reports carried over from window_manager
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 45/100
Rechercherichtung
Start with a Flutter app using the Window API and reproduce the ten linked window_manager reports on macOS. Check the related nativeapi#59 issue for context, then verify each report and either fix it or record that it no longer occurs. Done means every checklist item has a verified result.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.
Related: libnativeapi/nativeapi#59 (app-level hide on macOS).
- leanflutter/window_manager#565: buttons at the top of the window aren't clickable with a hidden title bar on macOS 26 Tahoe
- leanflutter/window_manager#171: a bar blocks the top of the content in native full screen
- leanflutter/window_manager#351: full screen together with always-on-top shows the menu bar and Dock
- leanflutter/window_manager#379: hide() while in full screen leaves a black screen
- leanflutter/window_manager#462: after setResizable(), the window can no longer be resized at all
- leanflutter/window_manager#501: on macOS 14+, the window can't be reopened after hiding it twice
- leanflutter/window_manager#543: crash when hiding the window from a global hotkey callback (with hotkey_manager)
- leanflutter/window_manager#541: setSize() hangs forever inside an integration test
- leanflutter/window_manager#481: background colour always black since Flutter 3.22.3 (reported on macOS)
- leanflutter/window_manager#360: app freezes after a hot restart when it starts in full screen (macOS, also reported on Windows 11)
- Vorherrschende Sprache
- C++
- Sterne
- 34
- Forks
- 7
- Ø Merge
- 3 T. 1 Std.
- Gemergte PRs (30 T.)
- 1
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus libnativeapi/nativeapi
-
bug
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 45/100
libnativeapi/nativeapi#81 ·
-
bug
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
libnativeapi/nativeapi#79 ·
-
bug
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 45/100
libnativeapi/nativeapi#78 ·
-
bug
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 45/100
libnativeapi/nativeapi#77 ·
-
bug
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 48/100
libnativeapi/nativeapi#76 ·
Alle Issues in libnativeapi/nativeapi
Ähnliche Issues
-
AuTest Bug Tests
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
apache/trafficserver#13714 ·
-
bug build
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
facebookincubator/velox#19143 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
tenstorrent/tt-metal#57393 · 1 Kommentar ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
objectionary/eo-graphs#74 ·