Updated ReactDOM.hydrate() documentation to explain the React 16 behavior. Please take note! https://reactjs.org/docs/react-dom.html#hydrate …pic.twitter.com/1D5mcI75ND
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Can you clarify? For text mismatches, we correct them on the client, and will add an explicit API in 16.1 to suppress that warning.
So it will be safe to have different text content. But not attributes.
Would love to discuss our different experiences with attributes. We work to keep them consistent. Perf hasn't suffered much afawct.
What's your use case? Patching up can also hide other differences like wrong event listeners/state, so not necessarily just better because.
Event listeners shouldn't run in server mode, right? I don't understand what you mean by use case...
Isn't it just an abstraction leak if you wind up with different DOM based on whether you SSRed or not? I can give examples but they seem obv
My argument is that you can end up with abstraction leak regardless if you patch up the attributes or not.
So you'd need a use case where that happens significantly more frequently with attributes, and patching them up is a satisfactory fix.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.