fix(material/chips): fix ripple element opacity when using CSS variable theming

[JoakimZebic]

Fixes a bug in the Angular Material chips component where ripple element doesn't have opacity when CSS variables are used to make a dynamic theme

Fixes #17577

[crisbeto]

The changes look good, but some of the CI checks are failing.

[JoakimZebic]

The changes look good, but some of the CI checks are failing.

Thanks for the review. I will take a look again at these tests, but I had some issues with executing them.

[crisbeto]

The test failures look like flakes so you should be able to resolve them by rebasing. The lint failure looks real though.

[JoakimZebic]

Thank you.
Lint failure is some trailing whitespace (most likely). I will look into it. :)

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[JoakimZebic]

@googlebot I fixed it.

[crisbeto]

The CLA error is because you pushed the commits from two separate email addresses.

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[crisbeto]

LGTM

[jelbourn]

LGTM

[mmalerba]

It looks like similar changes got merged in #17649, we can either rebase this one and merge it to extract the separate mixin, or just close it.

@jelbourn @crisbeto

[jelbourn]

@JoakimZebic this passes Google's internal presubmit, just needs a rebase

[mmalerba]

@jelbourn I took care of it

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