This repository has been archived by the owner on Jan 6, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 772
ngClass behavior change after latest nightly #428
Comments
Same problem here. Using |
ThomasBurleson
added a commit
that referenced
this issue
Sep 27, 2017
ClassDirective should work properly with `class` and `ngClass` usages; and only instantiate when responsive APIs are used. Fixes #428.
ThomasBurleson
added a commit
that referenced
this issue
Sep 27, 2017
ClassDirective should work properly with `class` and `ngClass` usages; and only instantiate when responsive APIs are used. * Add test that use @angular/material MdButtonModule md-raised-button * Update to use latest @angular/material Beta.11 Fixes #428.
ThomasBurleson
added a commit
that referenced
this issue
Sep 27, 2017
ClassDirective should work properly with `class` and `ngClass` usages; and only instantiate when responsive APIs are used. * Add test that use @angular/material MdButtonModule md-raised-button * Update to use latest @angular/material Beta.11 Fixes #428.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With latest release the below code is working perfectly:
<button mat-raised-button color="primary" type="submit" [ngClass]="{'btn-xs':formButtonXs}">Save</button>
But with latest nightly build, it no longer seems to work.
When value of formButtonXs is true the button has below classes:
mat-primary btn-xs
When value of formButtonXs is false the button has just below class:
mat-primary
Expected behavior
It should have
mat-raised-button mat-primary
whenformButtonXs
isfalse
whereas,mat-raised-button mat-primary btn-xs
whenformButtonXs
istrue
The text was updated successfully, but these errors were encountered: