-
Notifications
You must be signed in to change notification settings - Fork 23
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃殌 - autodetect anchor element's scroll container #175
Comments
@hakimio Thanks for your reply. Is the fix already included in the latest version or not? If yes, why is this the case? If you disable backdrop, it is still wrong |
Check issue #138 to see if the same solution of setting scroll container config fixes your issue as well. |
unfortunately not |
Seems to be working after setting |
The tour needs to know the scroll container for the animated scroll to work. Otherwise you can disable the animated scrolling if you don't want to deal with setting the scroll container. |
I thought about this a little bit more and I think it would be nice if the library could try to auto-detect anchor element's scroll container since it seems to be a common issue. If I have time, I'll take a look at this next week. |
Thanks for the help. It works now.
It would be better. I think that a line under the |
If you have some good ideas how to improve the docs, feel free to open a PR. |
Which ngx-ui-tour-* package is the source of the bug?
md-menu
Please provide a link to a minimal reproduction of the bug
https://stackblitz.com/edit/stackblitz-starters-9i9trv
Description
This problem is slimier to issue #152. If there is a scroll container and element scroll downs,
the correct position of the anchor element, mat-card and backdrop are not displayed.
If you click on previous button and go back to first element => again incorrect position of mat-card and backdrop
In #152 he had fixed somehow. but not said how.
Quick info: If you resized the window, everything is displayed correctly
Angular version
17.3.6
Ngx UI Tour version
12.0.3
Which browsers have you used?
Which operating systems have you used?
The text was updated successfully, but these errors were encountered: