Refresh page

[Ivan_Tellez]

@Mark_Levinson

After the user migrates away from the Default Web Page to a distant target page, and then tries to refresh the target page by clicking the browsers refresh (reload) button, the WebApp, instead, always returns the user to the Default page.

What you are talking about is Session restoration, this was announced as a Web 2.0 feature, BUT it was not implemented.

So, almost 2 years after the las web 1.0 release, web 2.0 is still feature incomplete:

Web2 automatic session restoring?

It’s a really important feature, it wasn’t ready but we are continuing to work on it for a subsequent release. Unfortunately, it didn’t get removed from some of the announcements.

All that HashTag changes and WebSession.SaveState could be used as a work around if you implement manually a system to save all the controls states, page variables, etc to restore them manually when the page refreshes (xojo opens first page, you read the states, load the las visited page and restore all the values to the page)

@Mark_Levinson

What is ‘best practice’ here?

Tell users not to refresh the page