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
{{ message }}
This repository has been archived by the owner on Apr 8, 2024. It is now read-only.
As far as I can tell from the source this is because the element's tag name is a generated UUID based on the current time, which will naturally differ between server and client.
Is there an option I can use to ensure this unique tag name is identical between the server and the client? The generic tag name core-dialog with no UUID would be enough for my purposes so I would be fine with a solution where I could disable the unique tag.
The text was updated successfully, but these errors were encountered:
The custom element is now rendered with the tag name core-dialog-react on both server and client. No warning from React (other than #261 which is unrelated).
I get this warning when using
@nrk/[email protected]
inreact16.8.6
in dev mode:The React documentation about hydration says that "you should treat mismatches as bugs and fix them"
As far as I can tell from the source this is because the element's tag name is a generated UUID based on the current time, which will naturally differ between server and client.
Is there an option I can use to ensure this unique tag name is identical between the server and the client? The generic tag name
core-dialog
with no UUID would be enough for my purposes so I would be fine with a solution where I could disable the unique tag.The text was updated successfully, but these errors were encountered: