-
Notifications
You must be signed in to change notification settings - Fork 6.8k
fix(selection-list): incorrectly handling A key in some cases #18513
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
Conversation
@@ -337,35 +337,35 @@ describe('MatSelectionList without forms', () => { | |||
it('should restore focus if active option is destroyed', () => { | |||
const manager = selectionList.componentInstance._keyManager; | |||
|
|||
spyOn(listOptions[2].componentInstance, 'focus').and.callThrough(); | |||
listOptions[3].componentInstance._handleFocus(); | |||
spyOn(listOptions[3].componentInstance, 'focus').and.callThrough(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some of these unrelated tests had to be tweaked, because I added an extra option to one of the fixtures.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, add merge-ready when ready
Fixes a couple of issues related to how the selection list handles the "A" key: 1. The typeahead doesn't work for the "A" key. It's because we were intercepting it earlier to support the "Select all" functionality. 2. Disables the ctrl + A shortcut in single selection mode, because it only makes sense during multi selection.
2b0998a
to
3566209
Compare
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Fixes a couple of issues related to how the selection list handles the "A" key: