Just wanted to say if you're looking to track down when the toasts page went up @ericwbailey.website added it last week!

Hey! Just wanted to say thanks for responding 🙏 super curious, for your external stylesheet how are you applying shadow DOM styles from it if they are rolled up into one?

I guess the thing for this would be that you would have a network request per custom element style you want to load in? e.g. you could bundle them and serve them together. Or is that not the case?

Thanks @keithamus.social ! Do you know of any good interim solutions or any that you’d recommend? I saw the issue listed out some but obviously not ideal. I’ve seen some hide the custom element until it’s defined as another way to mitigate this but then you can get pop in everywhere 😵‍💫

Very cool! I love it, thanks for sharing 🙏 I thought it was very interesting to have the `type` live on dropdown here for going between the different types of pickers (combobox, select, etc)

Thanks for sharing! Enjoyed taking a look 😄 Was curious what your take would be on how to do design something like this if the target/tooltip needed to support popovertarget/popover 👀 (if this one already does then ignore me lol)

For example, with a tooltip it'd be awesome to have a component with a slot for the trigger and the content but as soon as I mess around with the Shadow DOM I lose the ability to relate these with attributes for a11y. I had assumed this is what ElementInternals was used for but now I'm not sure 🤔

Hope you have a blast! 🥳

Exactly, this is using an older version of the tooltip so doesn’t use popover like the newer one does 😅

Also, excited that you’re coming back in a couple weeks!

I feel so lucky that I got to work with you when I first joined! Cheers to the next big thing, hope it's a blast 🍻

Feels like I'm missing something so obvious 🤔

For example, this codepen from Chris Coyier totally works: codepen.io/joshblack/pe... but then bringing it over into Next.js world it doesn't: codesandbox.io/p/devbox/3n9...

Just wanted to +1 the design systems use case! We’re starting to use it for Primer over at GitHub.

Definitely would make sense to me 👍 I think potentially changes to options could also be minor too depending on if they’re broadened vs narrowed.

Super curious, what makes you decide what feature set to cover for a component when looking across libraries?? 👀

God that would be nice, especially from a docs perspective. I feel like DS teams spend a lot of time on effective docs with good examples and I would love to bring these into the context for agent mode or even with things like copilot reviews to help bring guidance closer to everyone’s workflow

Also just wanted to say having something like this has also been very helpful for our move internally from the `sx` prop for styling with styled-components to CSS Modules. Wish we had something like this for our token change a couple years ago 😂