Deployed dev-app for 1f2ebfc to: https://ng-dev-previews-comp--pr-angular-components-31134-dev-pemcmxw4.web.app

Note: As new commits are pushed to this pull request, this link is updated after the preview is rebuilt.

In the demo I see that if I:

• turn multi off
• select just item 2 in the select
• click item 1

It toggles item 2 closed even though item 2's trigger is disabled. Is that the correct behavior? (genuinely not sure). I think it feels odd to me because the intent of the disabled trigger is like "hey user, you can't change this", but then if they toggle a different item they actually can

In the demo I see that if I:

• turn multi off
• select just item 2 in the select
• click item 1

It toggles item 2 closed even though item 2's trigger is disabled. Is that the correct behavior? (genuinely not sure). I think it feels odd to me because the intent of the disabled trigger is like "hey user, you can't change this", but then if they toggle a different item they actually can

You are absolutely correct. Agree that the expansion state for a disabled trigger shouldn't be changed. Fixed in the Expansion behavior to ensure the disabled triggers are excluded from the state changes.

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.}