Ilya Gurevich

@ronakrrb @mathisonian Neither of the solutions above will work for our use case unfortunately. In the first example above, the specific scenario we'd like to imagine is that the interactive...

@ronakrrb, unfortunately this proposal won't quite work as we don't quite have information on the actual contents of the resulting html we're inputting into dangerouslySetInnerHtml, this would require us to...

@rickhanlonii so the assumption here is that _any_ hydration mismatch will defer the entire root to a client-side re-render is that correct? I can dig a little more an reproduce...

@rickhanlonii I guess I'm also wondering why there's such a significant difference in behavior here between the previous hydrating behavior (which retained content rendered from dangerouslySetInnerHtml) even if there was...

@rickhanlonii, Thanks for the really well-described response. It's much appreciated. I will work on setting up a proper github repro soon to show what I'm talking about. I think you've...

@rickhanlonii coming back to you with a sandbox repo to reproduce this issue. Interestingly enough in the current example I provided above, this issue cannot be reproduced (assuming there are...

Closing as it looks like there are several things at play here: 1. Scripts running in dangerouslySetInnerHtml do _not_ create hydration mismatches 2. React 18 is much more strict about...

@himself65 just wanted to follow-up here, nytimes.com has recently migrated over to React 18 and are experiencing an influx of hydration mis-match errors that we hope to squash soon, however,...

@borgar I'm encountering similar issues in approach as well, you mention that it would be `impossible to test without a significant amount of code`, did you end up creating an...

@borgar thanks! I'll take a look into this, we have a similar contentEditable component in prosemirror we'd like to test.