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

feat(Timepicker): Implement a MAT_TIMEPICKER_SCROLL_STRATEGY for the component #30421

Open
laliconfigcat opened this issue Jan 30, 2025 · 0 comments
Labels
feature This issue represents a new feature or feature request rather than a bug or bug fix needs triage This issue needs to be triaged by the team

Comments

@laliconfigcat
Copy link

laliconfigcat commented Jan 30, 2025

Feature Description

First of all, thanks for the Timepicker component, I really waited for it and love it.

I'd have one feature request, I couldn't find a way to specify a scroll strategy for the component.
Like the MAT_MENU_SCROLL_STRATEGY, MAT_AUTOCOMPLETE_SCROLL_STRATEGY, MAT_SELECT_SCROLL_STRATEGY and MAT_DATEPICKER_SCROLL_STRATEGY for other components.
Scrolling can cause some crazy effects with the opened Timepicker. On material.angular.io it seems like this if i start scrolling:

Image

Would it be possible to implement a scroll strategy for the Timepicker too? Or if I am just missing something, could you please point me to the right direction?

Use Case

I'd like to control the scroll behaviour for the component.

@laliconfigcat laliconfigcat added feature This issue represents a new feature or feature request rather than a bug or bug fix needs triage This issue needs to be triaged by the team labels Jan 30, 2025
@laliconfigcat laliconfigcat changed the title feat(TimePicker): Implement a MAT_TIMEPICKER_SCROLL_STRATEGY for the component feat(Timepicker): Implement a MAT_TIMEPICKER_SCROLL_STRATEGY for the component Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature This issue represents a new feature or feature request rather than a bug or bug fix needs triage This issue needs to be triaged by the team
Projects
None yet
Development

No branches or pull requests

1 participant