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

Material chip list should support being not focusable #6069

Closed
mertdeg opened this issue Jul 26, 2017 · 4 comments · Fixed by #6073
Closed

Material chip list should support being not focusable #6069

mertdeg opened this issue Jul 26, 2017 · 4 comments · Fixed by #6073
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@mertdeg
Copy link

mertdeg commented Jul 26, 2017

Bug, feature request, or proposal:

Feature request

What is the expected behavior?

I should be able to pass in an @input() to mat-chip-list so that it doesn't have tabIndex = 0 by default. Sometimes we want to display chips within a tooltip. And we don't want user to be able to focus on individual chips.

What is the current behavior?

mat-chip-list is always focusable by default

What are the steps to reproduce?

Create mat-chip-list with non-zero chips inside

What is the use-case or motivation for changing an existing behavior?

To increase use cases for material chip list component

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

All

@mertdeg
Copy link
Author

mertdeg commented Jul 26, 2017

@jelbourn as FYI

@jelbourn jelbourn added the P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent label Jul 26, 2017
@jelbourn
Copy link
Member

@tinayuangao the chip list should respect a user-provided tabIndex if there is one

@bsteffl
Copy link

bsteffl commented Feb 7, 2019

This doesn't seem to make the chip appear to be not interactive when you click on the chip, it still has a ripple. Is there a way to have a readonly chip but is not disabled?

@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 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants