Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Prop `aria-owns` did not match. - SSR
See original GitHub issueShort description
I was trying to add react-geosuggest (v2.12.1) to a next.js (v9.1) application, however, I get a warning in my console: Warning: Prop aria-owns did not match. Server: "geosuggest__list_c2f6f86958fd7" Client: "geosuggest__list_b47ff6fa5019f"
Expected results
I expected the integration to work without warnings.
Actual results
I got a warning in the console, the culprit, in my opinion, is math.random generated listId in the Geosuggest.tsx.
Additional Information
Perhaps I am simply missing something here or the warning might not be relevant at all, however, I like to keep my console clean and wasn’t able to solve this on my own.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The random ID will be removed and it’s possible to set an ID on the Geosuggest to have aria-owns work even when there are multiple instances on a page. Thanks for reporting!
A release was due, the PR was just released in
2.13.1.