New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different react-a11y ids (server side render) #85
Comments
I have the same problem! |
I am also having this issue. |
A think solution could be using a hash derived from the dom tree from the element react-a11y creates. This should mean the IDs will match (I would hope so at least..). Ideally this is a strategy that is opted in to since there would have a perf. cost. Thoughts? |
@jasonmit I realize this issue is a little old, but did you verify that this solution worked? Any details on how to opt in to this? |
I am using React in isomorphic way, and have met warning message, after server side rendering. (You can reach message in attachments). How can I set react-a11 on client and on server? Thank you.
The text was updated successfully, but these errors were encountered: