Open ragnsan opened 6 days ago
Would you be able to update your studio version to 3.64.1
and check if that fixes the issue for you?
I’m currently using version 3.64.1, and I'm still experiencing the same issue.
After some exploration, I’ve identified the behavior more clearly. I started by running:
rm -rf .next node_modules
npm cache clean --force
npm install
npm run build
Initially, this seemed to fix the issue — there were no full page reloads when making changes in the presentation tool. However, upon publishing a document, the page refreshes, and the issue with refreshes on every modification reappears.
I've found that closing the page, disabling draft mode, and reopening it temporarily resolves the issue, but as soon as I publish a document from the presentation mode, the full page refresh on each change returns.
It seems that any action that triggers a full page refresh once causes it to persist for every subsequent change. Publishing is one example, but even toggling the edit mode (using the switch in the top-left corner) and re-enabling it causes a refresh.
The only way I’ve found to restore the normal behavior is by exiting draft mode completely.
These tests were done using npm run start
in Google Chrome.
If you find a security vulnerability, do NOT open an issue. Email security@sanity.io instead.
Describe the bug
Making changes in Presentation causes a full refresh / white flicker of the content in the left-hand pane.
To Reproduce
Steps to reproduce the behavior:
Any document viewed in the Presentation pane.
Screenshots If applicable, add screenshots to help explain your problem.
Which versions of Sanity are you using?
@sanity/cli (global) 3.28.0 (latest: 3.64.0) @sanity/asset-utils 2.1.0 (up to date) @sanity/color-input 4.0.1 (up to date) @sanity/icons 3.4.0 (up to date) @sanity/image-url 1.1.0 (up to date) @sanity/preview-url-secret 2.0.3 (up to date) @sanity/table 1.1.2 (up to date) @sanity/ui 2.8.23 (up to date) @sanity/vision 3.64.0 (up to date) sanity 3.64.0 (up to date) next-sanity 9.8.12
I was using next-sanity @ 9.8.10 and sanity @ 3.63.0 but I upgraded after seeing a similar issue on the official Sanity repo.
What operating system are you using?
MacOS
Which versions of Node.js / npm are you running?
10.2.4 v20.11.0