Netlify deploy preview

https://deploy-preview-931--base-ui.netlify.app/

Generated by 🚫 dangerJS against af718ab

Should we default to checking for computed styles if it's cheap, like inside an event, and falling back to the provider otherwise?

I thought about this, but we have to document DirectionProvider as a required step when changing the behavior is involved anyway to maintain that "there is one single way to set up RTL", even though technically it's not necessary (e.g. for ToggleGroup/RadioGroup)

And if a component doesn't actually use the provider internally it would obscure issues when someone used the provider but forgot to set dir

Floating elements force read the style and would ignore the provider,

@atomiks I think this should be fine for our components since only Menu is the only one that requires the provider (it has keyboard nav).

For the rest (popover, preview card etc), they should first use logical sides instead of left/right

I suppose since align: 'start'|'end' is already direction-aware without the provider, maybe side should be as well? 0a51ad1#diff-3edb30ade872773deda81b8799e55170e5a0a58fab8e2bee97a2210169e99066R95-R109