Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
md-list-item disabled property
See original GitHub issueBug, feature request, or proposal:
Proposal
What is the expected behavior?
Angular material2 list [disabled] item. An option to bind [disabled] to md-list-item in order to disable it (same as how the button disabled property works).
What is the current behavior?
no [disabled] property binding with md-list-item
What is the use-case or motivation for changing an existing behavior?
A list is not a button, but used for navigation and accessing data. [disabled] property can be very useful in such cases.
Which versions of Angular, Material, OS, browsers are affected?
All
Issue Analytics
- State:
- Created 7 years ago
- Reactions:9
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This makes a lot of sense to me. I have a md-nav-list and being able to disable some options depending on account settings seems appropriate. I think this would function the same as md-menu.
I understand that the native anchor element has no
disabledattribute but its hard to follow whya[mat-button]anda[mat-menu-item]usedisabledinput buta[mat-list-item]does not.