Skip to content
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

Wrap property for ListKeyManager #1608

Closed
kara opened this issue Oct 26, 2016 · 1 comment · Fixed by #1796
Closed

Wrap property for ListKeyManager #1608

kara opened this issue Oct 26, 2016 · 1 comment · Fixed by #1796
Assignees
Labels
Accessibility This issue is related to accessibility (a11y) feature This issue represents a new feature or feature request rather than a bug or bug fix

Comments

@kara
Copy link
Contributor

kara commented Oct 26, 2016

It would be nice if the ListKeyManager had a second mode where the focus doesn't wrap, but uses the alternate approach with HOME and END. Creating an issue to track, but still needs discussion before implementing.

Necessary for select implementation (#118).

@kara kara added the feature This issue represents a new feature or feature request rather than a bug or bug fix label Oct 26, 2016
@kara kara self-assigned this Oct 26, 2016
@kara kara added the Accessibility This issue is related to accessibility (a11y) label Oct 26, 2016
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Accessibility This issue is related to accessibility (a11y) feature This issue represents a new feature or feature request rather than a bug or bug fix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant