svippy wrote:

Each edit session uses a token to ensure that it is the same edit, and to avoid spam (and yes, to check for edit conflicts). As such, continued editing should always be using the edit link to produce a new token.

In other words, to allow this feature, you would require a new token to be produce when you use the back link, which ''will'' require a refresh of the page, thus rendering the purpose of this feature close to pointless.

If you're editing a full page, edit conflicts with yourself won't happen; they will happen for section edits though.

The issue is because the edit form includes 2 hidden input fields that have the revision timestamp of the revision you're editing and the time you started editing. These will both be wrong when using the back button. When you try to save the page, the server thinks you're editing an older version than you actually are. From a few minutes of looking, I can't find any way to force the browser to reload the page when using the back button that doesn't use some JS hack; but as Svip noted, if you have to reload the page, it somewhat defeats the purpose.