You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dimabutenko opened this issue
Jun 7, 2017
· 2 comments
· Fixed by #5305
Assignees
Labels
featureThis issue represents a new feature or feature request rather than a bug or bug fixP3An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
I want to not to render md-datepicker, so i added *ngIf="!control.isReadonly" to md-datepicker.
What is the current behavior?
When control.isReadonly is false, md-datepicker is not rendered
(I mean that there is no HTML for md-datepicker)
The text was updated successfully, but these errors were encountered:
jelbourn
changed the title
*ngIf in md-datepicker not working
Add ability to disable datepicker pop-up
Jun 8, 2017
jelbourn
added
feature
This issue represents a new feature or feature request rather than a bug or bug fix
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
labels
Jun 8, 2017
It's expected that this wouldn't work, since the component pulls the content of <md-datepicker> out of place and shows it in the floating panel. However, there should be a way to have this behavior.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
featureThis issue represents a new feature or feature request rather than a bug or bug fixP3An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Bug, feature request, or proposal:
Bug
I have a component with template like this:
What is the expected behavior?
I want to not to render md-datepicker, so i added *ngIf="!control.isReadonly" to md-datepicker.
What is the current behavior?
When control.isReadonly is false, md-datepicker is not rendered
(I mean that there is no HTML for md-datepicker)
The text was updated successfully, but these errors were encountered: