-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Themes are broken the first time a page is loaded #573
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
Comments
Yes, I can. |
Don't think that has changed in #550 - there is no validation now and there was no validation before as far as I can tell. |
EDIT: Ignore that. We may want to insert a check in |
Fixed in #574 🎉 |
I noticed that on
master
when you open up a book you've previously visited it'll be rendered without any CSS styling. This fixes itself when you change the themes and will never show itself again for that domain.I've seen something similar in the past where we'd changed the theme name being stored in local storage (because of a typo it went from
light
to"light"
, or vice versa). I believe the underlying issue is that when loading the theme we don't properly handle the case where the theme specified in local storage doesn't exist.I noticed this when rendering The Book as part of my final checks before pushing the 0.1 release. Unfortunately it blocks the release because styling will be broken for every single person who visits The Book (or any other document generated by
mdbook
) for the first time after this release and has been there before.@sorin-davidoi we may need to have a look at #550, possibly reverting it if there isn't an easy fix.
The text was updated successfully, but these errors were encountered: