Memory Forms, Document Expired on Back button click

[Stu]

Hi Folks,

I've got a lot of memory forms that house browses. Those browses open up forms. When the back button is clicked from a form, the user sees a "document expired" message (depends on browser what message they see).

Yes, the back button is evil. But it's not me that gets fired up about it, it's the consumer. And it doesn't help to explain about "security" and "forms" etc. They just want it to work. So in this specific situation (going back to a memory form) I'd like to help them out.

I've looked about a bit here for something recent, found http://www.nettalkcentral.com/index.php?option=com_smf&Itemid=36&topic=611.0;prev_next=next, but can't find anything (might not be looking right) that helps in this specific instance.

Is there a way to get a memory form to NOT be forgotten/expired when a user clicks the BACK button to it?

[Stu]

Hey Folks,

Bumpity .. Anyone got ideas on this?

[Bruce]

I have no ideas. The back button functionality changes from browser to browser, and in many (or most) cases does not send a request to the server at all. You're probably best off discussing this behavior with the folks at Mozilla or Google or Microsoft because this behavior is outside my control.

>> When the back button is clicked from a form, the user sees a "document expired" message (depends on browser what message they see).

exactly. The document has expired and needs to be refreshed. That's actually accurate.

cheers
Bruce

[Stu]

Hi Bruce,

I'm sensing frustration. Fair enough.

Let's break it down.

1. On a public site, webserver made in nettalk, I have a memory form with a browse in it.
2. I click on a link that opens a (memory or file) form from the browse within the memory form.
3. I click the BACK button.
4. The memory form and browse load fine.

This doesn't seem to work from within an Intranet (when logged in). (As per the question above)

I've just cottoned-on to something, it might be because the urls in the public site are hard-coded (ie, page name is filled in and used in links). Might be a red herring, but still.

Google doesn't give me a "document expired" message when I click the back button after googling something and going to a site.

If I had the power to override whatever it is that gives a "document expired" message, then I'd be happy. Because in particular situations I do not need the security kicking in (or whatever it is).

I guess I'm probably missing something fundamental.

[Bruce]

The bit you're missing is that the back button behavior is a function of the browser program, not the server. what it does, what messages it displays and so on is completely outside the scope of what the server does.

I can commiserate with you, and you're welcome to fiddle around to find behavior you'd like (I know I have) but I predict you will (a) discover that the behavior is anything but consistent, and (b) there are lots of arbitrary places where one thing works, but another thing fails, and (c) behavior from one browser to the next, and from one version of a browser to the next, can be very different.

In popup mode the problem largely goes away because the navigation there is more obvious, and if the user presses "back" then they go somewhere completely different. It's one (of many) reasons I prefer popup mode for "apps".

Of course you could spawn a browser instance without the back button at all - ie you have an index page which "opens" a new instance of the browser with your app, but personally I think that's even worse.

Of course give your users proper navigation so they don't need to press the back button - after that if they want to press it, but don't like the result, well I guess that's on them.

cheers
Bruce

[Stu]

Hi Bruce,

Thanks for taking the time.

I've just noticed something.

When I click around with the menu items, I can go "back" without issue.

It's when I use a custom-built link from a browse within a memory form and then try and go "back" that I get the document expired message.

Will investigate further.