What are you building? 👀

Not @ariakitjs, but @ariakit.org of course

… and let people follow the example 🔥

Any mentionable benefits you got from this strategy? How did it work in large orgs where you worked at?

So it’s for the content of the folder/folder items if I understand correctly

TreeFolderItems or TreeItems would maybe work better for me

I guess you want to avoid using prop? <TreeFolder items={children}>{item}</TreeFolder>

Looks solid, great that the virtualization is considered from initial API designs 👏

What’s not fully clear just from these examples — what is a difference between TreeFolder and TreeLevel?

Thank you also for the example with virtualization. Will there be also ComboboxRenderer, similarly as SelectRenderer?

Have you considered merging these 2 components together somehow? There are many similarities between them, and I see "searchable selects" more often now (especially in B2B patterns)

Thank you!

Tag looks awesome, and the example with integrated combobox is amazing — exactly what I was saying "it would be great to have it" 👏

I also welcome the change with the "integrated" combobox provider within Select component, which should make the last example a bit simpler too

Are the experimental features available somewhere already? 👀 Even if it's for testing still, happy to be part of that and provide feedback

Also curious about what changes are coming to Combobox API. Any chance there is public RFC/API design doc?

Thanks for any details you can already share

Tldr: From the first look, it appears very promising and as a good "base components companion" to my favorite Ariakit.

And not to forget that Base UI is still still in v1.0.0-alpha.

I really look forward to trying it out and seeing how Base UI will evolve in the future.

After Radix’s useful (but polarizing?) asChild prop, I wondered how Base UI would approach it.

They kept it simple: a `render` prop that can accept either a component or a function. Clean, flexible—thoughts?

base-ui.com/react/handb...

Tooltip has also one interesting prop: `trackCursorAxis`. It gives some flexibility to design decisions.

Additionally, it has a `hoverable` property that you can use when you need the tooltip to be interacted with further (e.g., when it contains a link)

If you've been working with dialogs or popovers, you know the struggles with focus management.

Base UI provides props to manage focus when opening but also when closing a dialog.

This will save some headaches.

Expandable components like Accordion or Collapsible feature a useful prop called `hiddenUntilFound`.

What does it do? It simply expands the item when someone searches for it using the built-in browser search. Great attention to detail.

What a great question. This article by @maggieappleton.com will explain it much better than I ever could and adds a list of interesting folks to follow on top of it

maggieappleton.com/design-engin...

Did you try to update to the latest version? I think it appeared after, together with a changelog

Imagine a call with a prototype in hands

If you want a really good deep dive into testing with screen readers, I strongly advise reading this guide by @sarasoueidan.com

www.sarasoueidan.com/blog/testing...

#a11y #screenReaders #accessibility

👋