Closed RasmusKjeldgaard closed 4 months ago
When inserting buttons asynchronously or based on some condition, the order of buttons as inserted in markup is not preserved.
This snippet, where Overview is expected to be the first element:
<kirby-tab-bar> <kirby-tab-button *ngIf="true" routerLink="overview"> Overview </kirby-tab-button> <kirby-tab-button routerLink="transfer"> Transfer </kirby-tab-button> ...
Is actually rendered like this, with Overview as the last element, because of the *ngIf directive:
*ngIf
See above.
9.3.2
Order as inserted in html is preserved.
The following tasks should be carried out in sequence in order to follow the process of contributing correctly.
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
The contributor who wants to implement this issue should:
Once the issue has been implemented and is ready for review:
Describe the bug
When inserting buttons asynchronously or based on some condition, the order of buttons as inserted in markup is not preserved.
This snippet, where Overview is expected to be the first element:
Is actually rendered like this, with Overview as the last element, because of the![image](https://github.com/kirbydesign/designsystem/assets/42470636/d5a57138-2187-4e89-93b4-75bc26383cdf)
*ngIf
directive:Describe how to reproduce the bug
See above.
Which Kirby version was used?
9.3.2
What was the expected behavior?
Order as inserted in html is preserved.
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: