bug(mat-chip-listbox): Harness getChips() does not return mat-chip

[felhag]

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

Hello,

When using MatChipListboxHarness.getChips() it only returns mat-chip-option elements, but not mat-chip. Because of this a mat-chip-listbox like this example cannot be tested using the listbox harness. Not sure what is the correct solution for this because it can be solved using mat-chip-set instead of listbox.

Possible solutions imho:

1. Change example to use mat-chip-set instead of mat-chip-listbox.
2. Change getChips() signature to return MatChipHarness[] which would be a breaking change.
3. Add an additional method like getStaticChips().

Reproduction

StackBlitz link: https://stackblitz.com/edit/qykqid

Expected Behavior

MatChipListboxHarness.getChips() should include mat-chip as well.

Actual Behavior

MatChipListboxHarness.getChips() only returns mat-chip-option.

Environment

• Angular: 17.0.1
• CDK/Material: 17.0.1
• Browser(s): -
• Operating System (e.g. Windows, macOS, Ubuntu): All

[zarend]

Hello,

Thank you for reaching out. Using mat-chip inside a mat-chip-listbox is unsupported behavior :). The only supported elements that may be used inside a mat-chip-listbox is mat-chip-option.

Best Regards,

Zach

[felhag]

Hey, thanks for the quick reply. But like I said, it's literally used that way in one of the examples which is kind of confusing. Shouldn't that be changed? I'm happy to provide a PR if you like.

[zarend]

Hello, sure, go ahead and send us a PR. We'd love to take a look.

-Zach

[felhag]

Took a while, but created a PR. Let me know what you think.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}