Hello Paul,

Hm, if you click on the "Back", it doesn't render a confirmation but if you refresh the page, it does.

Hi Mark

I don't think I've ever refreshed a page I'm on unless I'm viewing it and waiting for content to update to see if a change has been affected. 'Normal behaviour' (haha, when doing the wrong thing ) would be to accidentally navigate away from the current page without saving.

Hello Paul,

I agree, and to be honest, this was in the initial beta release but it seems like someone else had actually complained about the annoying popups when clicking on the back button, https://stackideas.com/forums/wrong-logic

Not sure if we should really add a settings for the back button behavior as it seems to be too excessive to have too many settings.

Hi Mark

When i read the thread relating to this, actually i think what has been suggested has:

1. Been misunderstood
2. Been acted upon without really seeing the risk of making the change
3. Been incorrectly applied

This is what is said at 5:41 PM Friday, 31 March 2017 # 5

1. You need a bigger and red Exit button - that is named Exit! The exit must be more obvious/intuitive by users. Why dish the red X on top right?

2. Get rid of the "Are you sure you want to leave this - SITE(!)" pop-up. At least re-phrase it to "Are you sure you want to leave and go back to your site/blog?"

In actual fact, i take from point 1, that by making the button red and naming it EXIT, you are making it really clear that you are Exiting Edit mode (which naturally comes with the risk unsaved changes could be lost)

With point 2, the person is saying, the problem is with the wording of the pop-up.... it suggested you are 'leaving the site', when the user is really just 'closing the authoring screen'. That's why he suggested the wording change to '...go back to your site/blog'.

I really think this either needs a clear warning for users that by hitting the back button, any unsaved changes will be lost. I envisage many user complaints.

Kind regards
Paul

Hm, yeah perhaps you are right. Let me discuss this with the team and see what we could do about this.