mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 04:46:56 +00:00
[GH-ISSUE #6803] [Bug] Can't reduce window size in full screen #3001
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#3001
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 @davystrong on GitHub (Nov 17, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/6803
Originally assigned to: @LucasXu0 on GitHub.
Bug Description
Hope I haven't missed anything obvious, but when I open Appflowy as a split window in fullscreen mode on Mac, the window can't be reduced below about two thirds of the screen.
How to Reproduce
Open the app in split screen mode alongside some other app
Expected Behavior
I would expect to have full control over the window size, or at least, that the minimum size would be a lot smaller.
Operating System
macOS
AppFlowy Version(s)
0.7.3
Screenshots
No response
Additional Context
No response
@LucasXu0 commented on GitHub (Nov 18, 2024):
Hi, @davystrong. We have a minimum window size requirement of 960 pixels to avoid UI scaling issues.
@davystrong commented on GitHub (Nov 18, 2024):
@LucasXu0 thanks for that! I'm using a 16 inch Macbook, the display is 3456 pixels across and I'd estimate it doesn't let me reduce it below about 2100 pixels. 960 would be reasonable, I think, but this is annoying. Any idea why it won't go any smaller?
@LucasXu0 commented on GitHub (Nov 18, 2024):
@davystrong My previous comment was not clear. For your MacBook, the limitation should be 960 × (2-3) pixels (approximately within this range). I may change it to a dynamic value based on the screen pixels if it doesn't cause too many UI issues.
@davystrong commented on GitHub (Nov 18, 2024):
@LucasXu0 that makes more sense. Yes, having it linked to the screen pixels might be a good idea, however I'd like it to be as flexible as possible. With the current window layout, it looks like the value could be reduced to about half what it currently is without any issues, even with the sidebar open. I had previously been using OneNote, and this actually something it did quite well. When the window got too small, the sidebar stopped "pushing" the content out of the way and start appearing in from of the content, then disappearing when you focused on the page again. Maybe this is something you could do as well.
@LucasXu0 commented on GitHub (Nov 26, 2024):
Hi, @davystrong. This package reduces the minimum window size limitation. Would you like to test to see if it matches your screen size?
https://github.com/AppFlowy-IO/AppFlowy-Builder/releases/download/0.7.4_main/AppFlowy-0.7.5-macos-universal.dmg
@davystrong commented on GitHub (Nov 26, 2024):
@LucasXu0 tested and that works much better now! Thank you! I'll close this issue.