You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With #1671 the input property usePopover was introduced to the dropdown. When this is enabled the PopoverComponent is used to position the pop-out box.
This was done in order to be able to solve the bugs mentioned in the description of the aforementioned PR.
usePopover is set to false by default as we're not certain if it will introduce any bugs. Per 14. March 2022, testing has begun where some consumers of Kirby try to set usePopover="true" for their dropdowns.
What's next?
The goal is to eventually have usePopover="true" be the default. To do this we must:
Solve any reported bugs from consumer projects testing the popover functionality (if any).
Decide in which major version we will make it default. As soon as we know, we should implement a deprecation warning, letting people know that the default value will be change.
In the decided major remove the usePopover input property and just use the functionality per default.
Where are we now?
With #1671 the input property
usePopover
was introduced to the dropdown. When this is enabled thePopoverComponent
is used to position the pop-out box.This was done in order to be able to solve the bugs mentioned in the description of the aforementioned PR.
usePopover
is set tofalse
by default as we're not certain if it will introduce any bugs. Per 14. March 2022, testing has begun where some consumers of Kirby try to setusePopover="true"
for their dropdowns.What's next?
The goal is to eventually have
usePopover="true"
be the default. To do this we must:usePopover
input property and just use the functionality per default.Issues popover will allow us to solve:
Related issues:
Other:
PopoverComponent
with their implementation.The text was updated successfully, but these errors were encountered: