Skip to content

bug(mat-tab-group): preserveContent not working #24432

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
stiles-j opened this issue Feb 16, 2022 · 2 comments
Closed
1 task

bug(mat-tab-group): preserveContent not working #24432

stiles-j opened this issue Feb 16, 2022 · 2 comments
Labels
needs triage This issue needs to be triaged by the team

Comments

@stiles-j
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

[preserveContent] does not work. Even in the Angular Material online documentation the [preserveContent] input is not working as expected.

Reproduction

Steps to reproduce:

  1. Create a mat-tab-group with at least two tabs where one of the tabs content contains an iframe
  2. Change tabs, the content in the iframe will not continue to play, or will the content stay loaded in the DOM

Expected Behavior

The content in the hidden tab containing the iframe should continue to play and continue to exist in the DOM

Actual Behavior

The content in the iframe stops playing and is removed from the DOM

Environment

  • Angular: 13.1.3
  • CDK/Material: 13.2.2
  • Browser(s): Chrome, Edge
  • Operating System (e.g. Windows, macOS, Ubuntu): Windows
@stiles-j stiles-j added the needs triage This issue needs to be triaged by the team label Feb 16, 2022
@crisbeto
Copy link
Member

The first version that has the feature is 14.0.0-next.2, but it looks like you're on 13. The docs currently have an issue where they're showing the API docs for the next feature. They'll be fixed once we release angular/material.angular.io#1123.

@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 Mar 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs triage This issue needs to be triaged by the team
Projects
None yet
Development

No branches or pull requests

2 participants