[GH-ISSUE #491] [Bug] Wrong Window placement if taskbar is on top (Windows) #231

New issue

Closed

opened 2026-03-23 20:34:12 +00:00 by mirror · 0 comments

mirror commented

2026-03-23 20:34:12 +00:00

Owner

Originally created by @apeyrat on GitHub (May 8, 2022).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/491

Originally assigned to: @appflowy on GitHub.

Describe the bug
I'm using Windows 11 with my taskbar located on top of my screen.
When starting appflowy, the appflowy menubar appear below my windows taskbar making the application unusable.

Tested with v0.0.4 beta3
This is not a regression, i faced the same issue with a previous version.

To Reproduce
Steps to reproduce the behavior:

On Windows,, move your windows taskbar on top (instead of bottom of screen as default)
Launch AppFlowy
Bug should be visible

Expected behavior

Screenshots

Desktop (please complete the following information):

OS: Windows 11

Additional context

Environment [e.g. flutter doctor -v or rustup show]
Add any other context about the problem here.

Originally created by @apeyrat on GitHub (May 8, 2022). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/491 Originally assigned to: @appflowy on GitHub. **Describe the bug** I'm using Windows 11 with my taskbar located on top of my screen. When starting appflowy, the appflowy menubar appear below my windows taskbar making the application unusable. Tested with v0.0.4 beta3 This is not a regression, i faced the same issue with a previous version. **To Reproduce** Steps to reproduce the behavior: 1. On Windows,, move your windows taskbar on top (instead of bottom of screen as default) 2. Launch AppFlowy 3. Bug should be visible **Expected behavior** **Screenshots** ![image](https://user-images.githubusercontent.com/32652100/167305989-3e17aad4-3a80-4ad2-8708-5e44d07df2fa.png) **Desktop (please complete the following information):** - OS: Windows 11 **Additional context** - Environment [e.g. flutter doctor -v or rustup show] Add any other context about the problem here.