bug(MatAutocomplete): BlockScrollStrategy doesn't work with cdkScrollable
- Lingua principale
- TypeScript
- Stelle
- 25k
- Fork
- 6.8k
- Merge medio
- 1g 8h
- PR unite (30g)
- 91
Descrizione
### 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
Using `BlockScrollStrategy` on `MatAutocomplete` does not work unless the scroll container is the document itself.
I've added `cdkScrollable` to the scroll container, and `CloseScrollStrategy` and `RepositionScrollStrategy` do work, but not `BlockScrollStrategy`.
### Reproduction
1. https://angular-scroll-block.stackblitz.io
2. Use Ctrl+Space inside the input field and scroll the scroll-container.
Working example with the scroll in the document:
1. https://angular-scroll-block-works.stackblitz.io
2. 2. Use Ctrl+Space inside the input field and scroll the document.
### Expected Behavior
Scroll should be blocked when using `BlockScrollStrategy`
### Actual Behavior
Scroll is not blocked when using `BlockScrollStrategy`
### Environment
Angular CLI: 14.2.3
Node: 18.12.0 (Unsupported)
Package Manager: npm 8.19.2
OS: win32 x64Angular: 14.2.2
... animations, cdk, common, compiler, compiler-cli, core, forms
... material, platform-browser, platform-browser-dynamic, routerPackage Version
---------------------------------------------------------
@angular-devkit/architect 0.1402.3
@angular-devkit/build-angular 14.2.3
@angular-devkit/core 14.2.3
@angular-devkit/schematics 14.2.3
@angular/cli 14.2.3
@ngtools/webpack 14.2.3
@schematics/angular 14.2.3
ng-packagr 14.2.1
rxjs 7.5.6
typescript 4.8.3
webpack 5.74.0
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia riproducendo il comportamento nell'esempio angular-scroll-block.stackblitz.io collegato e confrontalo con l'esempio document-scroll funzionante. Leggi gli entry point di MatAutocomplete e BlockScrollStrategy, quindi verifica che lo scorrimento del contenitore cdkScrollable sia bloccato mentre l'autocomplete è aperto, senza compromettere le altre strategie di scorrimento.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- angular, typescript
- Ambito
- frontend
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 42/100