fix(chips): default click action on chip being prevented

[crisbeto]

Fixes all the click actions on a chip being prevented. The action wasn't being prevented up until c82aca9 where it got moved out of the if (this.disabled). Since there isn't any info or tests around why it was done this way, I'm assuming that it was by accident.

Fixes #9032.

[jelbourn]

LGTM

[mbward]

Looks like the PR branch needs to be re-sync'd to pick up d527e48?

[mmalerba]

shouldn't we also check if it originates from the chip input?

[crisbeto]

That's not necessary, because the focus method checks whether the input is focused.

[vivian-hu-zz]

When trying to sync this PR into google, I found I need to do the following to make them pass:

1. revert the change made in src/lib/chips/chip-list.ts
2. change chip.ts into this:
   _handleClick(event: Event) {
   // Check disabled
   if (this.disabled) {
   event.preventDefault();
   } else {
   event.stopPropagation();
   }
   }

We can take a 2 step approach with the first step just to fix the default event handler bug, and handle the even propagation later since we will need to fix the broken test cases first.

[crisbeto]

@vivian-hu I've switched it back to always stop propagation. The important change in this PR is that we call preventDefault for disabled chips, I also removed the stopPropagation since it didn't look like there was a particular reason for 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.}