You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently use both htmlIdGenerator() (44 usages) and useGeneratedHtmlId() (46 usages) in our function components. useGeneratedHtmlId() calls htmlIdGenerator() internally when running on React 17 and lower (see #7078) and neither of these functions is SSR compatible, generating different results on server- and client-side.
Acceptance Criteria
All function components should use useGeneratedHtmlId() hook to generate unique identifiers
The text was updated successfully, but these errors were encountered:
👋 Hi there - this issue hasn't had any activity in 6 months. If the EUI team has not explicitly expressed that this is something on our roadmap, it's unlikely that we'll pick this issue up. We would sincerely appreciate a PR/community contribution if this is something that matters to you! If not, and there is no further activity on this issue for another 6 months (i.e. it's stale for over a year), the issue will be auto-closed.
Summary
We currently use both
htmlIdGenerator()
(44 usages) anduseGeneratedHtmlId()
(46 usages) in our function components.useGeneratedHtmlId()
callshtmlIdGenerator()
internally when running on React 17 and lower (see #7078) and neither of these functions is SSR compatible, generating different results on server- and client-side.Acceptance Criteria
useGeneratedHtmlId()
hook to generate unique identifiersThe text was updated successfully, but these errors were encountered: