Embeddable sandbox: do not force refresh on updates about apollo-server HOT 8 OPEN

thanks so much for the thoughtful steps in the screencapture 🙏

We're able to reliably reproduce the issue, have identified the problem and have a PR awaiting review

from apollo-server.

Hello! Thank you for this bug report. We will look into and update when we find a resolution.

from apollo-server.

Hi there, thanks so much for the bug report

Could you please help confirm a few things so we can make sure we're looking at the right thing? 🙏

Is it the case that the page is refreshing by itself, with no user interaction?
The codepaths that trigger a refresh are currently all in button click handlers, I can't imagine how that could be possible 🤔
It is the case that if you have multiple tabs open, clicking on "update" in one tab will trigger updates across all tabs, might that be what you experienced?

Wrt losing time and effort, we use localStorage to persist state, refreshing shouldn't cause lost work.
Was sandbox being opened in your browser's incognito mode?
Does refreshing a tab normally cause contents to be lost, or only if it was from an update? (how do you know the page refreshed from an update?)

from apollo-server.

Hi @cheapsteak,

To answer your question yes, the page is refreshing itself with no user interaction, that is, the user didn't request the page refresh. I have never seen any "update" button you're referring to, but having one and installing updates only when clicked or on manual page refresh would very much fix this issue.

As shown by this screen capture, you can see it takes roughly 10 seconds from the moment I access the page for the first time and the moment it reloads. I even used Incognito mode to make sure no extension or any other tab is interfering.

I have time to start building my document, and the page refreshes before showing again in its default empty state.

Now, I'm aware I can configure the embed to keep its state between refreshes with the persistExplorerState option, but in my opinion it's not a valid solution since it's still disruptive, and I'd like to avoid storing authorisation headers in the local storage.

from apollo-server.