Ripple Config

[csabattilas]

Bug, feature request, or proposal:

Change the ripple config for all buttons for example

What is the expected behavior?

What is the current behavior?

What are the steps to reproduce?

Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U

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

It prevents using css hacks and it's possible to fine tune the ripple for all elements for a certain type

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

Is there anything else we should know?

[devversion]

Great idea. I need to see how this should be done, because I want to avoid issues with the MD_DISABLE_RIPPLES token.

[devversion]

@krigton I was made aware of the fact that I misread the issue. I actually don't think it would be elegant to provide a DI token to only set options for the button component (or others).

If we would support such DI token, then we would need to do this for other components as well.

[csabattilas]

Yes, my idea was that or a global configuration which affects all the ripples, or each component could have it's own configuration

[devversion]

@krigton Yeah I misread it and understood you requested a config that affects all ripple elements.

Right now with #3463, developers are able to specify a global base-speed.

[csabattilas]

@devversion thanks, that's might be enough for us for now. thank you very much

[devversion]

@krigton You are welcome. Thanks for the idea!

[angular-automatic-lock-bot]

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.}