Can be challenging because portals change the tab order. But if you use the native HTML popover, you can escape clipping but keep DOM order the same, so I’d probably use that.

What if component libraries supported in-context errors by default via async React action props? Simple DX like toasts, but better UX. 🤔

All just CSS transitions – no additional animation libraries needed! We give you data-entering and data-exiting states for each TabPanel, and a CSS variable for the height that you can transition.

It's possible. We'll have an example in the new docs we're working on. stackblitz.com/edit/48ss6jk...

The current month is centered in the viewport, with an extra month + large placeholder on either side. As you swipe, the months update and the placeholder shrinks. When scrolling ends, the scroll position is re-centered. This avoids jumpiness when updating the scroll position while the user scrolls.

Thanks! It animates too. 😉

All of the colors are calculated based on a single CSS variable using relative oklch, so you can change the theme with just one line.

--tint: green;

Modern CSS is amazing! 😲

Dark mode 🌒

the golden era imo

Thanks!

In case you missed it, here’s the recording of my talk! www.youtube.com/live/p9OcztR...

Yes. We're still planning a TagField, which would allow "inline" editing of the tags (like the gmail "To" field). But you can get pretty close with Select + TagGroup + Autocomplete example I showed.

Yes! bsky.app/profile/devo...

Here's the demo shown in the video combining a Select with a TagGroup. You can add a TagGroup within a SelectValue and access the selected items via the render prop function. It also uses Autocomplete to allow filtering. Composition ftw! 😀

stackblitz.com/edit/rac-sel...

Cool. I've been testing it with some React Aria demos I'm working on. Very excited about it.

No ViewTransition? 😢