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
{{ message }}
This repository has been archived by the owner on Mar 13, 2023. It is now read-only.
I'm not overly concerned about this since browser cache should handle this pretty well already on subsequent visits, and it would make little difference on our platform since we serve a full page cache from Varnish to logged out users.
It is going on .org, but just saying any platform with a full-page cache and/or object cache makes this a non-issue. Would be interesting to see what the gain would be otherwise. Just store the CSS blob in a theme mod and serve that to logged out users?
I think it would make logical sense to cache the entire css output, rather than calculating it on the fly for every page load.
We can flush the cache when a customizer value changes and set the cache for the first user.
What do you think?
The text was updated successfully, but these errors were encountered: