-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Closed
hrueger/AGLight
#112Labels
P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentAn issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Description
Reproduction
https://stackblitz.com/edit/angular-qz4usp?file=src/app/expansion-steps-example.html
Steps to reproduce:
- in example, first panel is disabled and the second is not
- the first button will call "open" on the first panel, and the second, the second.
- notice that the first button doesn't work, but the second does
Expected Behavior
By calling "open" programmatically (via button click), I expect the disabled panel to open, as per the docs
Expansion panels can be disabled using the disabled attribute. A disabled expansion panel can't be toggled by the user, but can still be manipulated programmatically.
Actual Behavior
The disabled (first) panel won't open programmatically
Environment
- Angular: 8.2.9
- CDK/Material: 8.2.2
- Browser(s): chrome 79
- Operating System (e.g. Windows, macOS, Ubuntu): windows 10
Metadata
Metadata
Assignees
Labels
P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentAn issue that is relevant to core functions, but does not impede progress. Important, but not urgent