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
When material-ui is used in isomorphic websites, the following warning is found in the browser console:
Warning: React attempted to reuse markup in a container but the checksum was invalid. This generally means that you are using server rendering and the markup generated on the server was not what the client was expecting. React injected new markup to compensate which works but you have lost many of the benefits of server rendering. Instead, figure out why the markup being generated is different on the client or server:
(client) ght:24px;width:24px;-webkit-user-select:
(server) ght:24px;width:24px;user-select:none;fil
It seems that the auto-prefixing module breaks server-side rendering because browser prefix is only prepended in the browser and not on the server.
A plausible way to fix this, mentioned in FormidableLabs/radium#128 (comment), is to provide autoprefixer with user-agent data of the request. Not sure if this is suitable for material-ui though.
The text was updated successfully, but these errors were encountered:
MrOrz
changed the title
Auto-prefixing breaks server-side rendering, checksum mismatch.
Auto-prefixing breaks server-side rendering, warns "checksum mismatch".
Jun 4, 2015
MrOrz
changed the title
Auto-prefixing breaks server-side rendering, warns "checksum mismatch".
Auto-prefixing breaks server-side rendering with "checksum mismatch".
Jun 4, 2015
When material-ui is used in isomorphic websites, the following warning is found in the browser console:
It seems that the auto-prefixing module breaks server-side rendering because browser prefix is only prepended in the browser and not on the server.
A plausible way to fix this, mentioned in FormidableLabs/radium#128 (comment), is to provide autoprefixer with user-agent data of the request. Not sure if this is suitable for material-ui though.
The text was updated successfully, but these errors were encountered: