Amy Sorto

This is intentional as it is a part of the [M3 spec](https://m3.material.io/components/top-app-bar/specs). Althought yes the docs and examples should be updated to remove these custom colors that used to work...

I think it's awesome you want to contribute to this repository, I would love to help! It feels to me making the chips in your app to be unfocusable but...

The fix for this will be in the next patch (see the issue linked in the comment above for the relevant PR). Thanks for trying out MDC!

Could you provide more context and the link to the example? It seems like the details portion is empty. We ask people follow these [steps to create an issue](https://github.com/angular/components/blob/main/CONTRIBUTING.md#-submitting-an-issue).

On the top right hand side for the API page, you can see the testing section in the table of contents. I'll add a comment to #25614 to make sure...

I'll raise the priority to a P3, although we don't plan to work on this feature soon at this time. Although we would happily accept a community PR for this.

It would also be great if as a part of this, we can have a new tab for testing to make the documentation more discoverable.

It looks like that error is surfaced directly from the YouTube API. It's certainly odd that is cannot be reproduced either on your end. Its interesting you are only seeing...

Got it, okay that makes sense to me! Chips that are display only (not interactive). @ice-blaze Yes you are right, our docs get populated from the code comments throughout this...

Closing this issue since the MDC based chips are going to be in v15 which will be released soon