Closed yaboi closed 9 years ago
@yaboi I noticed that when i upgraded to 1.9.17, I saw the same thing. This has to do with the way the css file is cached in your browser. Lame, and i haven't found a work around yet but it should only happen during testing when we have our cache.manifest turned off.
Here's what I did:
Let's verify in prod when/if we can?
I know you're getting ready to release 1.10.x, but in the meantime, this is what it looks like when I load 1.9.17 (latest release)
This is full screen (lg) in Chrome