@angular/material 19: Datepicker integrated with Timepicker should not reset the time
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 25k
- Forks
- 6.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 91
Description
Which @angular/* package(s) are the source of the bug?
@angular/material
Is this a regression?
Yes
Description
Can be reproduced in the v19 example: https://material.angular.io/components/timepicker/examples#timepicker-datepicker-integration
Steps:
- use datepicker to select date
- use timepicker to select time
- change date - either via picker or type
Expected Result:
Time portion of the value should not change
Actual Result:
Time portion resets to 00:00
Please provide a link to a minimal reproduction of the bug
https://material.angular.io/components/timepicker/examples#timepicker-datepicker-integration
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run ng version)
"@angular/material": "19.0.3",
Anything else?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the v19 Datepicker and Timepicker integration example linked in the issue and reproduce the reset after changing the date. Trace the value handling for that integration, then verify that changing the date preserves the previously selected time instead of restoring 00:00.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100