Skip to content
This repository has been archived by the owner on Apr 20, 2023. It is now read-only.

Problem when using visibleActionsLimit = 0 #65

Open
vesper8 opened this issue Feb 27, 2022 · 1 comment
Open

Problem when using visibleActionsLimit = 0 #65

vesper8 opened this issue Feb 27, 2022 · 1 comment

Comments

@vesper8
Copy link

vesper8 commented Feb 27, 2022

In my case I have a resource with many detached actions, over 15 of them, so it doesn't make sense to show 1 or 2 and then show the rest in the menu, instead I just want to show all of them in the drop down menu. So when I set 'visibleActionsLimit' => 0, then it works, but because the menu popover shows on the right, it ends up going off-screen.

Screen Shot 2022-02-28 at 12 19 06 AM

Would it be possible to customize this behaviour so that it would open to the left instead of the the right when the limit is set to 0 ?

Or ideally this would be configurable, but if it would at least automatically default to the left when set to 0 then that would be great.

Thank you for this great package!

@vesper8
Copy link
Author

vesper8 commented Feb 27, 2022

The solution is to make the bottom-end here

<dropdown placement="bottom-end" dusk="detached-actions-invisible-buttons-dropdown">

Customizable. In my case I would like it to be bottom-start

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant