When using the dropdown configured with expand="block" [usePopover]="true" within a kirby-page the card popover doesn't show when opening the dropdown.
Describe how to reproduce the bug
Nest a kirby-dropdown within a kirby-page and configure it with expand="block" [usePopover]="true"
Click on the dropdown to toggle/open it
See the items not being shown
Which Kirby version was used?
9.3.2
What was the expected behavior?
The items being shown.
Are there any additional context?
Seems to be caused by the dropdown's ngAfterViewInit being run before the dropdown has a width, which is where the width of the card/popover is set when configured with popover+block. This is again caused by the ion-content element within kirby-page not having a width until it has been initialized.
Checklist:
The following tasks should be carried out in sequence in order to follow the process of contributing correctly.
Verification
To make sure the bug is not intended behaviour; it should be verified by a member of team Kirby before moving on to implementation.
[ ] Make sure the NOT verified label has been removed by a member of team Kirby; do not proceed until this is done.
Implementation
The contributor who wants to implement this issue should:
Describe the bug
When using the dropdown configured with
expand="block" [usePopover]="true"
within akirby-page
the card popover doesn't show when opening the dropdown.Describe how to reproduce the bug
kirby-dropdown
within akirby-page
and configure it withexpand="block" [usePopover]="true"
Which Kirby version was used?
9.3.2
What was the expected behavior?
The items being shown.
Are there any additional context?
Seems to be caused by the dropdown's
ngAfterViewInit
being run before the dropdown has a width, which is where the width of the card/popover is set when configured with popover+block. This is again caused by theion-content
element withinkirby-page
not having a width until it has been initialized.Checklist:
The following tasks should be carried out in sequence in order to follow the process of contributing correctly.
Verification
To make sure the bug is not intended behaviour; it should be verified by a member of team Kirby before moving on to implementation.
NOT verified
label has been removed by a member of team Kirby; do not proceed until this is done.Implementation
The contributor who wants to implement this issue should:
Review
Once the issue has been implemented and is ready for review: