-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
styles broken with JS's disabled #75
Comments
Are you running on |
It should at least render properly in production mode. However, as I mentioned in #62, this project is not really designed to work with javascript disabled. |
In dev mode, the styles are injected by the script that webpack dev server injects, so you get a brief FOUC. It's the price of having the hot reloading during development. |
This is not just a problem with JS disabled. It results in a FOUC in production (the Heroku build does this as well), as components using non-global classes doesn't have the className set when the server renders. If you log out Any ideas on to fix this? |
You are very correct. I will investigate. |
Any news on this @erikras? |
Not yet. Haven't gotten around to it, sorry. |
@ostrgard is it possible to reproduce it on the demo site? |
@dmitry Yes, the demo site exhibits this behavior. |
Since this project is not intended to support javascript disabled browsers, this issue will remain closed, but the FOUC is an important issue, so I've opened #153. |
+1 for the title. |
The text was updated successfully, but these errors were encountered: