Found a related issue:#15659
I'm going to expand on both of these issues and why they are hard to reproduce

Changing globals reloads the documentation page

This is related topreview.parameters.docs.container ordecorators - when you wrap the documentation page withThemeProvider that uses these globals, it reloads the page, not just rerenders the component. For some reason it doesn't do this in a stackblitz example - tried to remove components and simplify themain.stories array and at some point it fixed itself. So looks like SB only does this when there are a lot of components, maybe some race condition or performance bottleneck we're hitting. But this is just a guess. We have something like 50+ components, so nothing crazy.

Changing globals fails in some cases

received X but was unable to determine the source of the event - seems likeevent.source is undefined ingetEventSourceUrl:

So if I change that like to

event.source=rawEvent.origin;

this issue goes away. Most probably there's a reason this needs to happen, but want to say that the issue is ingetEventSourceUrl.ts I think.

Hello.

I've ran into something similar. The same issue happens to me in docs pages with "larger" stories. It indeed seems to be some race condition since the issue happens more frequently when stories grow bigger. It also happens more frequently in development than in production builds.
Another interesting thing is that it works fine when you change globals using theuseGlobals hook in a decorator.

I've made areproduction repo and hosted it with Chromatichere. I have use Material-UI but I don't think that is the actual cause. It seems to happen without MUI as well as long the render phase of the story is long/heavy.
Just note that Chromatic hosts a productional build and therefor you don't see the error in the console and neither does it happen as frequently.

Thanks@nukemonk, awesome example. Referenced this in the related issue.

This is how console looks like locally running it:

Any news on this? Experiencing it on8.1.11

I am having the same issue on 8.6.0

The issue still persists on Storybook 9.1.8. The only difference is that at least the selected value persists. So it does not sometimes use the old value anymore.