[GH-ISSUE #3493] [FR] Implement a safe area for popovers #1576

New issue

Open

opened 2026-03-23 20:51:15 +00:00 by mirror · 1 comment

mirror commented

2026-03-23 20:51:15 +00:00

Owner

Originally created by @richardshiue on GitHub (Sep 21, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/3493

Description

Our Popover implementations don't offer the cool triangle-safe-zone-menu-filter thingamabobs that makes navigation user friendly. As a result, all of our sub menus HAVE to be shown until dismissed, instead of hiding as soon as the mouse is out of the safe zone.

Impact

Any user that opens a nested poover

Additional Context

No response

Originally created by @richardshiue on GitHub (Sep 21, 2023). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/3493 ### Description Our Popover implementations don't offer the cool triangle-safe-zone-menu-filter thingamabobs that makes navigation user friendly. As a result, all of our sub menus HAVE to be shown until dismissed, instead of hiding as soon as the mouse is out of the safe zone. ### Impact Any user that opens a nested poover ### Additional Context _No response_

mirror added the

new feature

improvements

labels

2026-03-23 20:51:15 +00:00

mirror commented

2026-03-23 20:51:16 +00:00

Author

Owner

@Xazin commented on GitHub (Sep 21, 2023):

Hmm, this is a fun one.

Essentially there should be some space in the implementation.

This behavior shouldn't be enforced (Should be toggleable)
When no longer hovering the child of the popover or the popover itself, it should close.

It's important to keep in mind, that when the widget that triggers the popover is hovered, the popover should still stay open.

We can implement a different "safe area"-type if we need it later on, for not including the child of the AppFlowyPopover in the "safe area".

@Xazin commented on GitHub (Sep 21, 2023): Hmm, this is a fun one. Essentially there should be some space in the implementation. 1. This behavior shouldn't be enforced (Should be toggleable) 2. When no longer hovering the child of the popover or the popover itself, it should close. It's important to keep in mind, that when the widget that triggers the popover is hovered, the popover should still stay open. We can implement a different "safe area"-type if we need it later on, for not including the child of the AppFlowyPopover in the "safe area".

mirror referenced this issue

2026-03-23 22:16:29 +00:00

[PR #1772] [MERGED] fix: potential async errors #4935