Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Windows] Verify: full-screen transitions

Open
#77 0 comments 0 reactions 0 assignees View on GitHub

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
cpp

Research direction

Start with a Flutter app using the nativeapi Window API and reproduce each of the four linked full-screen reports on Windows. Check the related full-screen changed event issue for context, then determine for every item whether it still occurs and either fix it or record that it no longer happens. Done means all four checklist entries have been verified and updated.

Written by the indexing model from the issue text.

Description

bug

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#58 (full-screen changed event).

  • leanflutter/window_manager#458: after starting in full screen, setFullScreen(false) shows only the background colour; the taskbar icon disappears and minimize stops working
  • leanflutter/window_manager#579: title bar doesn't come back after leaving full screen
  • leanflutter/window_manager#569: a window created with WS_POPUP doesn't get its caption back when leaving full screen / setting TitleBarStyle.normal
  • leanflutter/window_manager#330: previous content visible at the bottom when switching to or from full screen (video player)
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from libnativeapi/nativeapi

All issues in libnativeapi/nativeapi

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.