🔮 Sanity Create is here. Writing is reinvented. Try now, no developer setup

Issue with menu popovers in Sanity, resolved by removing experimental configuration.

9 replies
Last updated: May 22, 2024
Hi, is anyone else having an issue with menu popovers from within sanity?
May 15, 2024, 2:20 PM
I'm following the guide (yet again) for live previews, so this is a completely fresh install, literally copy and pasting commands from the guide. Straight away in the install, these popovers aren't working, for anything.
The content appears to be in there, through looking in the dev tools. And you can click on where things should be. But the content is all hidden inside.
May 15, 2024, 2:23 PM
Looks to be an issue specifically with the css property "--motion-content-opacity: 0;"
This doesn't seem to change like it should, and thus no popovers show.
May 15, 2024, 2:23 PM
Tried downgrading sanity a few times with no success
May 15, 2024, 2:39 PM
So I just figured this out...
Removing:


experimental: {
	taint: true,
}
from my next.config.mjs fixed this issue entirely.
May 15, 2024, 2:58 PM
I’ve been having the same issue. And your solution works, however I wonder, what does
taint: true
do, is it safe to remove it?
May 22, 2024, 8:14 AM
Taint is an experimental feature that forces you to keep certain variables outside of the client, mostly API keys. That's also what it's used for here.
Removing it really shouldn't do anything, and I've got no idea why turning it on breaks the backend of Sanity at all
May 22, 2024, 8:16 AM
Alright, thanks for the info! Yeah, it’s strange that doing this fixed the issue.
May 22, 2024, 8:19 AM
Ahaa, and right now I ran into this 😄
May 22, 2024, 8:21 AM
Yeah, just remove the taint function. As that's technically what you've disabled.
May 22, 2024, 8:56 AM

Sanity– build remarkable experiences at scale

Sanity is a modern headless CMS that treats content as data to power your digital business. Free to get started, and pay-as-you-go on all plans.

Was this answer helpful?