-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
bug(mat-date-range-picker): Focus indicator is not present for the selected date #22883
Labels
Accessibility
This issue is related to accessibility (a11y)
area: material/datepicker
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Comments
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jun 14, 2021
Currently there's no way to tell when the selected date in the calendar has focus. These changes reuse the styling from when the selected date is today (white circle inside the main circle). Fixes angular#22883.
Hello, Does enabling strong focus indicators fix this problem? |
Reproducible on Windows but not macOS This is a regression from Angular v12. Both v13 and v14 have this issue now |
Still an issue in Angular 18. See this example from https://material.angular.io/components/datepicker/overview: When the focus is on either the selected start date or the selected end date, there is no focus indicator at all. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Accessibility
This issue is related to accessibility (a11y)
area: material/datepicker
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Reproduction
Steps to reproduce:
Expected Behavior
Provide a focus indicator or drop shadow in addition to the background color change
Actual Behavior
Focus indicator is not present for the selected state of date's present inside date range picker. Hence it is difficult for the users to know where the focus is
Environment
The text was updated successfully, but these errors were encountered: