Align MDC-based chip harnesses with existing MatChipHarness

[jelbourn]

The MDC-based chip harness is missing several APIs from the original due to some implementation differences between the two. We need to bridge this before the MDC-based component is considered fully stable.

[MatteoVH]

I'm taking on the addition of the remove method for the MatChipHarness.

[crisbeto]

FYI we've discussed among ourselves how we want to approach this. The first step is #20817.

@MatteoVH so you don't end up wasting time on it: you may not be able to implement the remove method right now, because removal depends on a transitionend event. While we do have an API that will allow you to dispatch it, it currently isn't possible to set the propertyName property of the event which MDC is looking for. There's a pending PR (#20764) to make it possible to change the propertyName.

[MatteoVH]

Hi Kristiyan,

My fix (#20831) shouldn't be affected by #20801, but thank you for the heads up.

When testing my PR by using the harness in my unit tests, it seems like the custom width propertyName doesn't actually matter. The (removed) output is still triggered and the HTML element is correctly removed from the DOM.

[MatteoVH]

Hey, looks like I was wrong and the width propertyName is necessary. My project's unit test was passing for other reasons that were unrelated (still not sure why, exactly.) I'll wait for #20764 to be merged.

[crisbeto]

Resolved in #21051.

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