MatSidenavContainer scroll events not working as documented
See original GitHub issueBug, feature request, or proposal:
Bug
What is the expected behavior?
Able to react to scrolling inside the <mat-sidenav-container>
What is the current behavior?
Unhandled Promise rejection: Cannot read property ‘scrollable’ of undefined ; Zone: <root> ; Task: Promise.then ; Value: Error: Cannot read property ‘scrollable’ of undefined TypeError: Cannot read property ‘scrollable’ of undefined at new SidenavResponsiveExample
What are the steps to reproduce?
https://stackblitz.com/edit/angular-rgkuk8?file=app/sidenav-responsive-example.ts
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to detect scroll events in mat-sidenav-container
With fullscreen property above any of the window methods like window.scroll() and the properties like window.pageYOffset will not work.
Read more >Sidenavcontainer Scrollable Elementscrolled (forked)
Starter project for Angular apps that exports to the Angular CLI.
Read more >Sidenav - Angular Material
Returns observable that emits when a scroll event is fired on the host element. ... since browsers are not consistent about what scrollLeft...
Read more >Sidenav | Angular Material
Returns observable that emits when a scroll event is fired on the host element. ... since browsers are not consistent about what scrollLeft...
Read more >Sidenav | Angular Material
Reacting to scroll events inside the sidenav container. To react to scrolling inside the <mat-sidenav-container> , you can get a hold of the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Reopening the issue since the PR got in by accident and had to be reverted.
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.