Pro 6 Beta 4 - Prompt regarding unsaved work when switching tabs

Beta
#1

I thought the discussion around this was that we weren’t having a prompt. (That said I don’t mind having it. )

If the prompt is removed again I would like to retain the prompt when switching to different builder elements from within the preview. I.e. switching from the page to the header. This prompt should also have the three options mentioned below.

Secondly in the previous betas, except 3, it was possible to switch between tabs and unsaved work was retained.

Is this no longer possible or has it been done for performance reasons?

In Pro 5 with the prompt we are asked if we want to “Continue and save”. I think, if we are having the prompt, this is an important option to prevent time wasting.

Ideally we then need three options.

  • Continue and save
  • Yes, Proceed
  • No, go back

It is quite annoying to need to have to select “No, go back”, then save and then switch tabs again.

#2

So there is no more “Edited” highlight anymore? We cannot switch tabs without saving first? That makes tabs pretty useless I’d say.

I want to go back and forth between pages, sometimes simply to grab some text or copy something else. I cannot save the tab in works since it is not finished yet. (If I’m editing something on a live page). I think the “Edited” label on tabs makes much more sense.

#3

@urchindesign / @Misho

So there was this thread from Beta 3, which mentioned issues with losing edits after switching tabs. I can’t find it, but I felt like there was another one where a prompt was suggested to mitigate this (or perhaps it was my mixing up the need for a prompt if a user accidentally clicked the “Edit Header” observer on a page for instance).

At any rate, to clear up any confusion below is the proposed functionality based on the mechanics and feedback we’re seeing:

  1. If multiple tabs, and the current tab you’re on is changed in any way, it will display an “Edited” label in the tab indicating something has changed. Switching from that tab to another doesn’t need a prompt because you might just want to switch quickly to look at something and then come back and continuing with your work. You shouldn’t need to save to switch tabs from the Document Bar, but your edits should remain as you move back and forth between documents.
  2. If navigating to another Document from within a Document (i.e. clicking the “Edit Header” observer when on a page), this should trigger a prompt, as these clicks could happen unintentionally while moving through the page. If confirming on the prompt that you want to move to the new Document, if the page you are on has edits, like the above, it should maintain it’s “Edited” stage and all edits and persist if you come back.

Please confirm with me that the above is correct when you have a moment. Thanks.

1 Like
#4

I’ve had a page open in one tab, and a global block in another tab. I observed 2 types of behaviors in the same install, shortly after each other:

  1. I quickly went to look at something in the global block, then came back to the page. All changes I had done to the page were lost.
    Edit: I don’t recall if I changed something in the global block and saved it. The page displays the global block. Maybe this relationship / dependence caused a reset of the page to the unsaved state?
  2. Wanted to replicate this. Added an element to the the page. But now, when trying to switch to the global block in the other tab, I got the warning dialog mentioned above.
    In neither case this reflects the behavior you describe, @kory.
    (I wanted to post this issue here yesterday, but I still cannot anymore create posts in the forum. Glad somebody else mentioned it so that I can reply and report)
#5

@striata, the cases I outlined above are my proposed changes, not what is currently in.

In my response I mentioned that I believe the current setup of prompts got incorrectly wired up based on other forum discussions. I am asking if #1 and #2 above are the desired behaviors from users in this forum. From my seat, they are the desired behaviors, but are not how it currently is. I’m just trying to gain consensus so I can have an actionable path forward with our team.

Thanks.

1 Like
#6

My apologies, but I forgot to mention this as well about why we put in the prompt while switching tabs. Let’s say you had the following scenario:

  • A Page open and a Header open.
  • You make a change on your Page so your first section is red, let’s say, but you don’t save that page.
  • You navigate to the Header tab, and make a change so your header is yellow, but you don’t save.
  • As you navigate back and forth between these contexts, previously it wasn’t able to show you these changes because they aren’t saved. Even after saving it wouldn’t always display until after a refresh due to the caching of styles.

This is another scenario to take into account with all of this. We are still discussing some of this internally. This will likely need a little more exploration of the best possible compromise of all scenarios.

#7

Okay. To answer your question: I like the scenario you have outlined.

#8

@kory, what you describe here sounds good. It’s logical.

#9

Thanks, I’ve noted this down. There are some other things we’re needing to consider and nail down here, but this helps.

1 Like
#10

I am also happy with what you have described.

#11

Thanks again!

#12

Sounds good to me as well!

Too confirm, natural behaviour in my view is that we can switch between tabs freely without ever losing edits, and without prompts. We do have the “Edited” highlight and a prompt appears only if we try to close an unsaved tab (and also when clicking the header, footer, etc).

Thanks!

#13

Thanks, @Misho!

1 Like
#14

Not sure if this was brought up already:

Beta 4: If we make changes in a document and don’t save, opening a new document from the list loses all edits in the document that was open.

1 Like
#15

Switching to a new tab loses saved info? Is that the same for if you click a header

Sounds like this has to be a bug surely as what is the point of tabs if they lose the changes?

1 Like
#16

Hey everyone…I believe we have the game-plan mapped out here based on feedback from this thread and elsewhere. Please await the next release where this should all be finally resolved.

3 Likes