[GH-ISSUE #3218] [Bug] Slash Menu Overlay Clipped When Screen is Small #1419

New issue

Closed

opened 2026-03-23 20:48:59 +00:00 by mirror · 2 comments

mirror commented

2026-03-23 20:48:59 +00:00

Owner

Originally created by @a-wallen on GitHub (Aug 16, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/3218

Bug Description

I don't know exactly how to reproduce, but the slash menu is clipped for some reason when the screen is small.

How to Reproduce

Make the app as small as possible and trigger the slash menu.

Expected Behavior

The slash menu is shown in full

Operating System

Windows 10

AppFlowy Version(s)

main

Screenshots

No response

Additional Context

No response

Originally created by @a-wallen on GitHub (Aug 16, 2023). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/3218 ### Bug Description I don't know exactly how to reproduce, but the slash menu is clipped for some reason when the screen is small. ### How to Reproduce Make the app as small as possible and trigger the slash menu. ### Expected Behavior The slash menu is shown in full ### Operating System Windows 10 ### AppFlowy Version(s) main ### Screenshots _No response_ ### Additional Context _No response_

mirror

2026-03-23 20:48:59 +00:00

closed this issue
added the
Q3 24

bug

editor

2024

needs design
labels

mirror commented

2026-03-23 20:49:00 +00:00

Author

Owner

@a-wallen commented on GitHub (Aug 16, 2023):

@a-wallen commented on GitHub (Aug 16, 2023): related to https://github.com/AppFlowy-IO/AppFlowy/issues/1329

mirror commented

2026-03-23 20:49:00 +00:00

Author

Owner

@Xazin commented on GitHub (Aug 16, 2023):

I know this isn't the proper solution, but currently we have a max amount of items per column (5 I believe), this is extremely bad when you have too many items, as the slash menu becomes wider.

I was thinking we should implement an option, to dynamically allocate columns based on available size for the slash menu, as well as items.

This means that at the lowest possible width, the slash menu would be a one-column scrollable view. Since we have keyword search, I think it's valuable also for projects using the editor. If there is space for 2 columns, then it would distribute items equally amongst the two columns.

What do you think about this concept? I believe we have fixed width for an item, so we know the minimum size needed per column in the slash menu, and can thus calculate it on-demnad.

@Xazin commented on GitHub (Aug 16, 2023): I know this isn't the proper solution, but currently we have a max amount of items per column (5 I believe), this is extremely bad when you have too many items, as the slash menu becomes wider. I was thinking we should implement an option, to dynamically allocate columns based on available size for the slash menu, as well as items. This means that at the lowest possible width, the slash menu would be a one-column scrollable view. Since we have keyword search, I think it's valuable also for projects using the editor. If there is space for 2 columns, then it would distribute items equally amongst the two columns. What do you think about this concept? I believe we have fixed width for an item, so we know the minimum size needed per column in the slash menu, and can thus calculate it on-demnad.

mirror referenced this issue

2026-03-23 22:15:32 +00:00

[PR #1419] [MERGED] fix: #1413 [Bug] Azrty keyboard not opening menu when typing / #4724