Switching builders without saving leaves you in a permanently "unsaved state" – Beta 6

Beta
#1

Basically, if you have an unsaved change on a page, and you try to navigate to another builder, the Save button will stay Yellow and you’ll be told you have unsaved changes on each subsequent page – even if you don’t make changes.

Repro:

  1. Load a builder, and make one tiny change on the page
  2. Note that the Save button is now yellow
  3. Open the hamburger menu, and choose Header, Footer, Content, or Layout
  4. Click the edit button on one of the available pages/layouts
  5. When prompted that you have unsaved changes, select “Yes, Proceed”

Observed:
When the next page/layout loads, the save button will immediately be Yellow. If you now switch to yet another page/layout, you will again be prompted that you have unsaved changes (even if you didn’t make any changes). And so on and so on. (See video below)

I’m not sure what changes it thinks are unsaved. After recording that video, I went back and tried an experiment where I made an obvious change on the first page. Then went through two more pages, and finally clicked Save. Then, I went back to the first page, and that obvious change wasn’t saved. :man_shrugging:

By the way, moving through pages/layouts when all changes are Saved works fine. It’s just if there’s an unsaved change somewhere in there that it gets weird.

Loading Layouts, Content, or Headers scrolls down to the Footer – Beta 6
#2

Thanks @devinelston,

I’ll check this one out as soon as I can and report back here.

#3

Fixed for the next patch. I also split up tracking when a builder needs to be saved, and the rest of the things that get saved like colors, fonts, etc. There are two cases that will trigger a warning:

  • You make changes in a builder and try to leave that builder
  • You make any change and try to close the browser window

So you might still see the button stay yellow if you change something like a preference and leave the current builder.

1 Like