Repository navigation
refactor(mosaic): replace Floating UI Composite with useComposite - #10573
alexcarpenter wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🦋 Changeset detectedLatest commit: 64251fc The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/electron
@clerk/electron-passkeys
@clerk/eslint-plugin
@clerk/expo
@clerk/expo-biometrics
@clerk/expo-google-signin
@clerk/expo-native-components
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/mosaic
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
Description
Replaces Floating UI's
Composite/CompositeItemwith an in-houseuseCompositehook, so tabs, segmented control, accordion, action bar, tag input and the table's grid navigation share one roving-tabindex implementation. This removes the render-prop wrappers and is a step towards using Floating UI only for positioning.FloatingList/useListItem. It uses a ref-backedMaprather than state, because no index is needed.useListNavigation, OTP keeps its own handling, and the table keeps its DOM lookups for cells and widgets.tabindex, whereCompositeItemrendered them all as-1. The hook writestabindexin a layout effect, which doesn't run on the server. After hydration there is one tab stop, as before.Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change