Skip to content

Opened expansion panels do not save their state in virtual scroll #14781

Closed

Description

@alibenmessaoud

What is the expected behavior?

When scrolling on a list of expansion panels with the first one opened and then returning back to the top, the first panel should still be opened.

What is the current behavior?

Scrolling will open others expansion panels that have the same position as the first one, also it misbehaves the UI.

What are the steps to reproduce?

Just scrolling here after opening the first expansion panel: https://stackblitz.com/edit/angular-md-scrolling

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Angualr 7, MD 7, TS 3

Is there anything else we should know?

Same thing if you choose to open the nth expansion panel on the list.
Used the ngx-infinite-scroll works well and keeps opened expansion panels state. So it is about MD Scrolling.

Authors: @hzitoun @alibenmessaoud

Activity

  1. changed the title [-]MD Scroll misbehave on opened expansion panels[/-] [+]MD Scroll misbehaves on opened expansion panels[/+] on Jan 10, 2019
  2. changed the title [-]MD Scroll misbehaves on opened expansion panels[/-] [+]Opened expansion panels do not save their state in virtual scroll[/+] on Jan 10, 2019
  3. added
    P4A relatively minor issue that is not relevant to core functions
    on Jan 10, 2019
  4. added
    P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
    GThis is is related to a Google internal issue
    and removed
    P4A relatively minor issue that is not relevant to core functions
    on Feb 5, 2019
  5. crisbeto commented on Nov 25, 2025

    @crisbeto
    Member

    I don't think we can do much about this. As far as the expansion panels are concerned, they've been destroyed and re-created.

  6. angular-automatic-lock-bot commented on Dec 26, 2025

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

  7. locked and limited conversation to collaborators on Dec 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    GThis is is related to a Google internal issueP3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentarea: cdk/scrollingarea: material/expansion

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions