Skip to content

bug(Expansion Panel): Expansion Panel is set to closed, but is open and then gets closed being inside the Stepper #24480

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 task
nilokadnedzar opened this issue Feb 25, 2022 · 3 comments
Labels
needs: clarification The issue does not contain enough information for the team to determine if it is a real bug

Comments

@nilokadnedzar
Copy link

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

When you have a closed Expansion Panel as part of the Stepper it is open and then gets closed. It should be closed right away.

This only happens when the default animation of the Stepper is enabled.

Reproduction

Steps to reproduce:

  1. Put a closed Expansion Panel into the first step of the Stepper
  2. Keep default animation enabled of Stepper
  3. Reload app mutiple time

Expected Behavior

Expansion Panel should be closed right away.

Actual Behavior

Expansion Panel is open for some milliseconds and then gets closed.

Environment

  • Angular: 13.2
  • CDK/Material: 13.2.4
  • Browser(s): Chrome 98.0.4758.109
  • Operating System (e.g. Windows, macOS, Ubuntu): macOS Monterey 12.2.1
@nilokadnedzar nilokadnedzar added the needs triage This issue needs to be triaged by the team label Feb 25, 2022
@zarend
Copy link
Contributor

zarend commented Feb 28, 2022

Hello, we took a look at this and couldn't reproduce. Could you please provide a stackblitz reproduction of the issue?

@zarend zarend added needs: clarification The issue does not contain enough information for the team to determine if it is a real bug and removed needs triage This issue needs to be triaged by the team labels Feb 28, 2022
@crisbeto
Copy link
Member

crisbeto commented Mar 2, 2022

This should be the same root cause as #22785.

@crisbeto crisbeto closed this as completed Mar 2, 2022
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Apr 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs: clarification The issue does not contain enough information for the team to determine if it is a real bug
Projects
None yet
Development

No branches or pull requests

3 participants