Out-of-sync server/client ids [NDS-22]
sh0ji opened this issue · 2 comments
sh0ji commented
While looking more deeply into #92, I realized that the issue of internal component ids is quite complex and is not fully resolved. Specifically, as implemented, there's no guarantee that the server's initial hydration of the components will generate the same IDs as the client, which could cause issues in isomorphic applications.
This is addressed by quite a few of other systems and libraries:
- @react-aria/utils -
useId
- @fluentui/react-hooks -
useId
- @accessible/use-id (forked from @reach-ui/auto-id)
Also note that the incubating Accessibility Object Model (AOM) spec proposes a DOM-like solution to this where we wouldn't be required to use ids to set ARIA relationship properties, making this whole thing much easier. Setting relationship properties without needing to use IDREFs.
sh0ji commented
dmedjordan commented
Issue linked to JIRA Story: NDS-22