Components: Can't bind to 'matRippleDisabled' since it isn't a known property of 'div'

Created on 13 Jan 2018 · 5Comments · Source: angular/components

Bug, feature request, or proposal:

Bug

What is the expected behavior?

Should bind to div

What is the current behavior?

Can't bind to 'matRippleDisabled' since it isn't a known property of 'div'. ("tRipple class="mat-button-ripple" [class.mat-button-ripple-round]="_isRoundButton || _isIconButton" [ERROR ->][matRippleDisabled]="_isRippleDisabled()" [matRippleCentered]="_isIconButton" [matRippleTrigger]="_ge"): ng:///AppModule/MatButton.html@0:172
Can't bind to 'matRippleCentered' since it isn't a known property of 'div'. ("at-button-ripple-round]="_isRoundButton || _isIconButton" [matRippleDisabled]="_isRippleDisabled()" [ERROR ->][matRippleCentered]="_isIconButton" [matRippleTrigger]="_getHostElement()">

@0:214
Can't bind to 'matRippleTrigger' since it isn't a known property of 'div'. ("ton || _isIconButton" [matRippleDisabled]="_isRippleDisabled()" [matRippleCentered]="_isIconButton" [ERROR ->][matRippleTrigger]="_getHostElement()">

"): ng:///AppModule/MatButton.html@0:250

What are the steps to reproduce?

Providing a StackBlitz/Plunker (or similar) is the best way to get the team to see your issue.

Plunker starter (using on @master): https://goo.gl/uDmqyY

StackBlitz starter (using latest npm release): https://goo.gl/wwnhMV

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

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

"@angular/animations": "^5.0.0",
"@angular/cdk": "^5.0.4",
"@angular/common": "^5.1.3",
"@angular/compiler": "^5.0.0",
"@angular/core": "^5.2.0",
"@angular/flex-layout": "^2.0.0-beta.12",
"@angular/forms": "^5.0.0",
"@angular/http": "^5.0.0",
"@angular/material": "^5.0.4",
"@angular/platform-browser": "^5.0.0",
"@angular/platform-browser-dynamic": "^5.0.0",
"@angular/router": "^5.0.0",
"angular2-jwt": "^0.2.3",
"core-js": "^2.4.1",
"primeng": "^5.0.2",
"rxjs": "^5.5.2",
"zone.js": "^0.8.14"

Is there anything else we should know?

Source

mat-luc

Most helpful comment

@mat-luc to resolve the new error, add the module to imports instead of declarations. More details on https://stackoverflow.com/questions/45032043/uncaught-error-unexpected-module-formsmodule-declared-by-the-module-appmodul

emaillenin on 14 Aug 2018

🎉1 😄1

All 5 comments

@mat-luc you most likely haven't imported MatRippleModule

benb7760 on 13 Jan 2018

i did not import MatRippleModule. Thank you so much for pointed out.

mat-luc on 13 Jan 2018

I imported MatRippleModule, now i got new error,
Unexpected module 'MatRippleModule' declared by the module 'AppModule'. Please add a @Pipe/@Directive/@Component annotation.
I can't find that module in node-modules
Please help
Thank you

mat-luc on 13 Jan 2018

👍1

emaillenin on 14 Aug 2018

🎉1 😄1

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[bot] on 9 Sep 2019

Was this page helpful?

0 / 5 - 0 ratings