bug(Listbox): Can not select first option with Enter after calling .goToFirst() (@angular/aria)
- Dominant language
- TypeScript
- Stars
- 25k
- Forks
- 6.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 91
Description
### 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
When calling `.goToFirst()` the first option is set active. But it is not possible to select it with _Enter_. If the user hits _arrow down_ one time you can select the first option. But my whole reason for calling `.goToFirst()` is so the user do not need arrows when first option is the one they want.
I suspect an underlying keyboard manager is not being synced when calling `.goToFirst()'
### Reproduction
StackBlitz link: https://stackblitz.com/edit/go-to-first-issue-angular-aria-wpcbw3sz?file=src%2FApp.ts
Steps to reproduce:
1. Load stackblitz
2. Hit enter
Hitting enter should trigger en alert with the text "Option 0", but it does not happen
### Expected Behavior
When calling `.goToFirst()` the first option is selected and hitting Enter on the keyboard will select it.
### Actual Behavior
Nothing happens when hitting Enter
### Environment
- Angular: 21.1.3
- CDK/Material: 21.1.3
- Browser(s): Edge, Firefox
- Operating System (e.g. Windows, macOS, Ubuntu): Windows, Macos
Contributor guide
Research direction
Start with the linked StackBlitz reproduction, especially src/App.ts, and reproduce the .goToFirst() then Enter sequence. Investigate the suspected keyboard-manager synchronization and verify that pressing Enter after moving to the first option triggers an alert containing "Option 0" without requiring Arrow Down.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100