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
I just checked a couple sites using custom.min.css and there doesn't seem to be any cache busting on the URL. Is that intentional? It seems like it isn't the behavior we would want as users would have to do a hard refresh to get the latest version of custom.min.css loaded. Should we add a file timestamp to the end of the url or some version number or revision number so it forces browsers to get a new copy?
The text was updated successfully, but these errors were encountered:
I just checked a couple sites using custom.min.css and there doesn't seem to be any cache busting on the URL. Is that intentional? It seems like it isn't the behavior we would want as users would have to do a hard refresh to get the latest version of custom.min.css loaded. Should we add a file timestamp to the end of the url or some version number or revision number so it forces browsers to get a new copy?
The text was updated successfully, but these errors were encountered: