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 I try out the example app, I sometimes see a FOUC in Chrome: when the page loads, the components are rendered before the css is loaded. This causes the components to appear unstyled for a short moment. You may have to stroke F5 multiple times to see this effect.
I've only experienced this effect in Chrome, other browsers I tried (Firefox, Edge) do fine.
The text was updated successfully, but these errors were encountered:
That said, you make a good point on the FOUC. To avoid it, Webpack's extractTextPlugin can generate a separate css file for the production build (run via npm run build).
To clarify, the build script doesn't currently do so, so I'll look into making that happen.
When I try out the example app, I sometimes see a FOUC in Chrome: when the page loads, the components are rendered before the css is loaded. This causes the components to appear unstyled for a short moment. You may have to stroke F5 multiple times to see this effect.
I've only experienced this effect in Chrome, other browsers I tried (Firefox, Edge) do fine.
The text was updated successfully, but these errors were encountered: