mirror of
https://github.com/BoostIO/BoostNote-App.git
synced 2026-04-26 21:05:55 +03:00
[GH-ISSUE #740] App window not maximizing #382
Labels
No labels
android 🤖
assigned to core 🦹
bug 🐛
documentation 📚
documentation 📚
duplicate 🚫
external issue 🔼
external issue 🔼
feature request 🌟
funded on issuehunt 💵
help wanted 🆘
improvement request 🔨
improvement request 🔨
ios 🍎
mobile 📱
needs investigation 🔬
needs more info ℹ️
needs specs 📐
plugin idea 🔌
plugin idea 🔌
poll 🗳️
pull-request
question ❓
rewarded on issuehunt 🎁
security issue 🔑
won’t fix ❌
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/BoostNote-App#382
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ibdf on GitHub (Dec 24, 2020).
Original GitHub issue: https://github.com/BoostIO/BoostNote-App/issues/740
Current behavior
On most mac apps (non-native apps included) double clicking the top bar maximizes the app's window 100% of the screen. This is not fullscreen mode, which is possible by clicking the top left round green button, in this case the mac top menu bar is still visible. BoostNote does not follow this behavior... double clicking on the top bar of BoostNote does nothing.
Expected behavior
Double clicking the top bar should maximize the app's window 100% of the monitor screen vertically (except for the mac menu bar height) and 100% horizontally... without going into fullscreen mode.
Steps to reproduce
Open BoostNote and double click the top section of the app's window.
Environment
macOs - 11.1
@Flexo013 commented on GitHub (Dec 26, 2020):
Could you also mention what version of BoostNote.next you are using?
@ibdf commented on GitHub (Dec 28, 2020):
Version 0.11.5
@Rokt33r commented on GitHub (Aug 20, 2021):
Should be fixed by now. I cannot reproduce this issue anymore.