-
Notifications
You must be signed in to change notification settings - Fork 27
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
stickyThing not working inside a mat-sidenav-content #25
Comments
Hey @ciukstar, thank you for your report! I just gave it a shot in a forked StackBlitz and I can confirm the issue you are describing. I already have a suspicion, Material sets the content component to Repro: |
It would be great if My concrete scenario is a Thanks a lot! |
Hello, I have a similar issue, I am trying to use stickyThing inside absolute position element. Hopefully there is a solution. Thanks! |
Please test with version 1.1.2. You can now specify the scroll container element. Not sure if any usecase is covered, my minimal example currently covers a position absolute element that has a scroll bar: https://w11k.github.io/angular-sticky-things/posa In order to specify a scroll container:
Use anything that can be evaluated by Waiting for your feedback! ( fyi @kaihenzler ) |
Awesome, I think this should work fine, will test later. Thank you! |
I just tested, and it works, thanks! Small issue I encountered. Thanks again. |
Thanks for the review. Yepp, its a known issue that has already been fixed by another user. Will be released soon! #26 |
Yes it works. Thank you very much! |
I still cannot make it work. Tried everything mentioned in the comments one by one... |
It worked for me when I did it like this:
It gets the element there in time for the directive to find it. @anelad |
Hi!
It seems that
stickyThing
is not working "inside" amat-sidenav-content
of amat-sidenav-container
. Is it possible to make it work? How aboutstickyThing
"inside" amat-sidenav-content
of amat-sidenav-container
of amat-sidenav-content
of amat-sidenav-container
?Thanks!
The text was updated successfully, but these errors were encountered: