-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
Live reload issue when both HTML and CSS changes #12600
Comments
bep
added a commit
to bep/hugo
that referenced
this issue
Jun 15, 2024
This seems to be a browser bug (tested in both Chrome and Safari on MacOS), but it seems that doing a `window.location.reload()` (or `window.location.reload(true)`) doesn't refresh the CSS changes, even if HTTP caching is disabled. This commit works around this by doing additional refreshes of the CSSes. Closes gohugoio#12600
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
While testing the new
defer
feature, I found a peculiar issue in (at least) Chrome and Safari.This is the typical "TailwindCSS workflow." I have previously recommended a workflow that watches the
hugo_stats.json
for changes, and in that setup, this isn't an issue (you get 2 builds, first the HTML, then the CSS).But if you build both in one Go, we do a full browser reload, and the HTML change is visible, but not the CSS change (no fingerprinting of the CSS file).
This situation can be detected, and I have tested that this works:
The text was updated successfully, but these errors were encountered: