bug(datepicker): Focus Not Properly Managed After Selecting Date in Angular Datepicker (VoiceOver, iOS)
- Vorherrschende Sprache
- TypeScript
- Sterne
- 25k
- Forks
- 6.8k
- Ø Merge
- 1 T. 8 Std.
- Gemergte PRs (30 T.)
- 91
Beschreibung
### Is this a regression?
- [ ] Yes, this behavior used to work in the previous version
### The previous version in which this bug was not present was
_No response_
### Description
The Angular date picker doesn't properly focus on the selected date when using VoiceOver on iOS. When I try to select a date, the calendar opens as expected, and I double-tap to choose a date using VoiceOver. However, after the date is selected, the double-tap also triggers a selection on whatever element is behind the calendar.
### Reproduction
Steps to reproduce:
1. Enable VoiceOver on iOS.
2. Navigate to [Angular Material Datepicker](https://material.angular.dev/components/datepicker/overview).
3. Open the datepicker; the calendar overlay appears.
4. Using VoiceOver, double-tap to select a date.
5. After the double-tap, focus unexpectedly shifts to an element behind the calendar instead of remaining within the datepicker.


### Expected Behavior
After selecting a date using VoiceOver, the focus should return to the datepicker input, not shift to elements behind the calendar.
### Actual Behavior
After selecting a date with VoiceOver, the focus shifts to an element behind the calendar instead of returning to the datepicker input.
### Environment
- Angular: 18, 20
- CDK/Material: 18, 20
- Browser(s): Safari, Chrome, Brave
- Operating System (e.g. Windows, macOS, Ubuntu): iOS
Beitragsleitfaden
Rechercherichtung
Beginne damit, das Problem aus der Angular Material Datepicker-Übersicht unter iOS mit VoiceOver anhand der aufgeführten Schritte zu reproduzieren. Untersuche die Fokusbehandlung des Datepickers nach der Datumsauswahl und überprüfe, dass der Fokus zum Datepicker-Eingabefeld zurückkehrt und nicht zu einem Element hinter dem Kalender; decke das Verhalten mit einem Regressionstest ab, falls die vorhandenen Datepicker-Tests es sichtbar machen.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- angular, typescript
- Bereich
- accessibility, frontend
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 42/100