It seems that button press ripple effect stays in Chrome inside Sidenav, but not in Firefox or Safari.

[Nikki1993]

Bug, feature request, or proposal:

Bug

What is the expected behavior?

When the button with ripple effect enabled is pressed, after ripple animation concludes, the effect disappears at the end.

What is the current behavior?

Pressing the button keeps the ripple effect after it ends (when the button is located inside sidenav), making button background gray until unfocused or another button is pressed.

What are the steps to reproduce?

1. Create new sidenav
2. Insert a button via inside unordered list
3. Click the button
4. See ripple animation get stuck on Chrome but work perfectly fine on Firefox and Safari.

http://plnkr.co/edit/1jNN5lejEuo8VTIk3vsw?p=preview

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

The unintended behavior I suppose.

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

Latest Angular 2.x branch, Material beta 2

Is there anything else we should know?

[kara]

Looks like a dupe of #3215. Should be fixed in #3294.

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