Westbrook Johnson

Great sessions all. Be sure to continue the conversation in the various [discussions](https://github.com/w3c/webcomponents-cg/discussions) opened around this.

If I omitted something in some way, it was by no mean intentional. Feel free to create any issues, discussion, or whatnot that I may have missed trying to cover...

@e111077 started adding in some Slot Content Detection content for Wednesday... https://w3c.github.io/webcomponents-cg/2023.html#css-slot-content-detection

This is yet again another great reason to native behavior mixins to be surfaced to custom element authors (and in a declarative way). I know that's a whole other spec...

@annevk it would be great for there to be a way for a custom element to (say that it is a button and) participate in this API. 👏🏼 👏🏼 👏🏼...

> I.e., something like `this.#internals.button = "submit"` (or "`button`" for a plain button). As `[popover]` has full x-browser support and a growing number of related features, it would be great...

Cross-shadow root is one thing, I mean a big thing! However, if `` does not have a `` in it, for reasons like it being in a `buttongroup` or similar...

Browser support for this is pretty important to development at Adobe. Our [Spectrum Web Components library](https://opensource.adobe.com/spectrum-web-components) (leveraged in Photoshop, Express, soon to be Illustrator, and many more major efforts at...

> @Westbrook are you relying on the slot behavior in stable chrome? I am trying to remove it but running into issues in chrome:// pages which also rely on it...

Any chance we'll see a merge/release on these features sometime soon?