Skip to content
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

bug(CdkVirtualScrollViewport): "CdkVirtualScrollViewport is already attached" error appears when using nested virtual scroll #30245

Open
1 task
Malinxwski opened this issue Dec 28, 2024 · 0 comments
Labels
needs triage This issue needs to be triaged by the team

Comments

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

17.0.0

Description

"CdkVirtualScrollViewport is already attached" error appears when using virtual scroll inside another virtual scroll.

Reproduction

StackBlitz link: https://stackblitz.com/edit/stackblitz-starters-hrzgjwqz?file=src%2Fmain.ts
Steps to reproduce:

  1. Focus on input field (autocomplete component)
  2. Check console to see the error

Expected Behavior

CdkVirtualScrollViewports do not conflict with each other when nested virtual scroll is used.

Actual Behavior

Nested virtual scroll not working.

Environment

Angular CLI: 18.2.12
Node: 22.0.0
Package Manager: npm 10.5.1
OS: darwin arm64

Angular: 18.2.13
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
... service-worker

Package Version

@angular-devkit/architect 0.1802.12
@angular-devkit/build-angular 18.2.12
@angular-devkit/core 18.2.12
@angular-devkit/schematics 18.2.12
@angular/cdk 18.2.14
@angular/cli 18.2.12
@schematics/angular 18.2.12
rxjs 7.8.1
typescript 5.4.5
zone.js 0.14.10

Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 YaBrowser/24.10.0.0 Safari/537.36

@Malinxwski Malinxwski added the needs triage This issue needs to be triaged by the team label Dec 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage This issue needs to be triaged by the team
Projects
None yet
Development

No branches or pull requests

1 participant