Return to previous page

[staeri]

I use javascript:history.go(-1) to return to the previous page.

I've now found out that when returning to the previous page all
selections that the user made in dropdownlists are lost. How can these
be kept when returning?

I'm very grateful for fast response.

// S

[Stan]

On 15 May, 07:10, [e-mail] wrote:

I use javascript:history.go(-1) to return to the previous page.

I've now found out that when returning to the previous page all
selections that the user made in dropdownlists are lost. How can these
be kept when returning?

I'm very grateful for fast response.

// S

The previous data is lost because the browser has no way of retaining
it.

You have to use postback events to do the redirection and store the
data in session state.

[Peter Bucher [MVP]]

Hello Staeri

How do you return to the last Page?
If with "history.go(1);, all should work as expected,
because you are only navigating on the browser history.

--
Gruss, Peter Bucher
Microsoft MVP - Visual Developer ASP / ASP.NET, Switzerland
http://www.aspnetzone.de/ - ASP.NET Zone, die ASP.NET Community
http://www.aspnetzone.de/blogs/peterbucher/ - Auf den Spuren von .NET

[Mark Rae [MVP]]

"Peter Bucher [MVP]" <pe**********@aspnetzone.dewrote in message
news:07**********************************@microsof t.com...

How do you return to the last Page?
If with "history.go(1);, all should work as expected,
because you are only navigating on the browser history.

Clearly, that won't do what the OP wants, because that will simply open the
previous page as it was previously opened... Changes to DropDownLists,
TextBoxes etc will not be "remembered" because ASP.NET has no way of
"remembering" them unless as a result of a postback...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

[Mark Rae [MVP]]

<st****@gmail.comwrote in message
news:3e**********************************@56g2000h sm.googlegroups.com...

>I use javascript:history.go(-1) to return to the previous page.
I've now found out that when returning to the previous page all
selections that the user made in dropdownlists are lost.

Obviously. When you hit the Back button (either directly or in the above
code), the browser opens the previous page in exactly the same way as it was
previously opened - it has no way of "remembering" any client-side
modifications made to that page unless they were posted back...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

[staeri]

On 15 Maj, 10:15, "Mark Rae [MVP]" <[e-mail]:

<[e-mail] in message

news:3e**********************************@56g2000h sm.googlegroups.com...

I use javascript:history.go(-1) to return to the previous page.
I've now found out that when returning to the previous page all
selections that the user made in dropdownlists are lost.

Obviously. When you hit the Back button (either directly or in the above
code), the browser opens the previous page in exactly the same way as it was
previously opened - it has no way of "remembering" any client-side
modifications made to that page unless they were posted back...

--
Mark Rae
ASP.NET MVPhttp://www.markrae.net

Thank you for the answers!

I've stored the dropdownlist selections in sessions but is there a way
to set the dropdownlist selections to the session values when the page
is showed again when clicking the return button with
javascript:history.go(-1)? If it can be made without changing the url
I'm very happy because otherwise there are a lot changes I have to
make because of iframe etc.

// S

[Eliyahu Goldin]

Sure. You just need to restore selection from the session in the Page_Load
event.

--
Eliyahu Goldin,
Software Developer
Microsoft MVP [ASP.NET]
http://msmvps.com/blogs/egoldin
http://usableasp.net
<st****@gmail.comwrote in message
news:91**********************************@34g2000h sh.googlegroups.com...

On 15 Maj, 10:15, "Mark Rae [MVP]" <[e-mail]:

><[e-mail] in message

news:3e**********************************@56g2000 hsm.googlegroups.com...

>I use javascript:history.go(-1) to return to the previous page.
I've now found out that when returning to the previous page all
selections that the user made in dropdownlists are lost.

Obviously. When you hit the Back button (either directly or in the above
code), the browser opens the previous page in exactly the same way as it
was
previously opened - it has no way of "remembering" any client-side
modifications made to that page unless they were posted back...

--
Mark Rae
ASP.NET MVPhttp://www.markrae.net

Thank you for the answers!

I've stored the dropdownlist selections in sessions but is there a way
to set the dropdownlist selections to the session values when the page
is showed again when clicking the return button with
javascript:history.go(-1)? If it can be made without changing the url
I'm very happy because otherwise there are a lot changes I have to
make because of iframe etc.

// S

[staeri]

On 15 Maj, 11:18, "Eliyahu Goldin"
<[e-mail]:

Sure. You just need to restore selection from the session in the Page_Load
event.

--
Eliyahu Goldin,
Software Developer
Microsoft MVP [ASP.NET]http://msmvps.com/blogs/egoldinhttp://usableasp.net

<[e-mail] in message

news:91**********************************@34g2000h sh.googlegroups.com...

On 15 Maj, 10:15, "Mark Rae [MVP]" <[e-mail]:

<[e-mail] in message

>news:3e**********************************@56g2000 hsm.googlegroups.com...

I use javascript:history.go(-1) to return to the previous page.
I've now found out that when returning to the previous page all
selections that the user made in dropdownlists are lost.

Obviously. When you hit the Back button (either directly or in the above
code), the browser opens the previous page in exactly the same way as it
was
previously opened - it has no way of "remembering" any client-side
modifications made to that page unless they were posted back...

--
Mark Rae
ASP.NET MVPhttp://www.markrae.net

Thank you for the answers!

I've stored the dropdownlist selections in sessions but is there a way
to set the dropdownlist selections to the session values when the page
is showed again when clicking the return button with
javascript:history.go(-1)? If it can be made without changing the url
I'm very happy because otherwise there are a lot changes I have to
make because of iframe etc.

// S- Dölj citerad text -

- Visa citerad text -

It looks like Page_Load isn't fired when returning to the page by
using javascript:history.go(-1). Is that correct?

// S

[Eliyahu Goldin]

This means the browser gets it from the cache. location.reload(true) will
always go to the server. You need to think how to combine both history and
location calls.

--
Eliyahu Goldin,
Software Developer
Microsoft MVP [ASP.NET]
http://msmvps.com/blogs/egoldin
http://usableasp.net
<st****@gmail.comwrote in message
news:12**********************************@2g2000hs n.googlegroups.com...
On 15 Maj, 11:18, "Eliyahu Goldin"
<[e-mail]:

Sure. You just need to restore selection from the session in the Page_Load
event.

--
Eliyahu Goldin,
Software Developer
Microsoft MVP [ASP.NET]http://msmvps.com/blogs/egoldinhttp://usableasp.net

<[e-mail] in message

news:91**********************************@34g2000h sh.googlegroups.com...

On 15 Maj, 10:15, "Mark Rae [MVP]" <[e-mail]:

<[e-mail] in message

>news:3e**********************************@56g2000 hsm.googlegroups.com...

I use javascript:history.go(-1) to return to the previous page.
I've now found out that when returning to the previous page all
selections that the user made in dropdownlists are lost.

Obviously. When you hit the Back button (either directly or in the
above
code), the browser opens the previous page in exactly the same way as
it
was
previously opened - it has no way of "remembering" any client-side
modifications made to that page unless they were posted back...

--
Mark Rae
ASP.NET MVPhttp://www.markrae.net

Thank you for the answers!

I've stored the dropdownlist selections in sessions but is there a way
to set the dropdownlist selections to the session values when the page
is showed again when clicking the return button with
javascript:history.go(-1)? If it can be made without changing the url
I'm very happy because otherwise there are a lot changes I have to
make because of iframe etc.

// S- Dölj citerad text -

- Visa citerad text -

It looks like Page_Load isn't fired when returning to the page by
using javascript:history.go(-1). Is that correct?

// S

[Mark Rae [MVP]]

<st****@gmail.comwrote in message
news:91**********************************@34g2000h sh.googlegroups.com...

I've stored the dropdownlist selections in sessions

Ah - you didn't mention that in your original post...

but is there a way to set the dropdownlist selections to the session
values
when the page is showed again when clicking the return button with
javascript:history.go(-1)? If it can be made without changing the url
I'm very happy because otherwise there are a lot changes I have to
make because of iframe etc.

iframe? You didn't mention that either in your original post...

Anyway, as I see you've already discovered, session won't help you here
because the page is being fetched from cache. Therefore, you'll need to find
some way of preventing this which, depending on how you've set your app up,
will be either fairly trivial or next to impossible:

http://www.google.co.uk/search?hl=en...ge+cache&meta=
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

[Patrice]

What is the purpose of using the back button ?

The intended use is to display the previous page as it was previously seen
by the user. You could also prevent this page from being cached browser side
so that it is fetched again from the server (and possibly then updated).

Or perhaps should you implemnt your own link. What is the meaning of using
the back button in your case ?

--
Patrice

<st****@gmail.coma écrit dans le message de groupe de discussion :
3e**********************************...oglegroups.com...

I use javascript:history.go(-1) to return to the previous page.

I've now found out that when returning to the previous page all
selections that the user made in dropdownlists are lost. How can these
be kept when returning?

I'm very grateful for fast response.

// S

[staeri]

On 15 Maj, 13:20, "Patrice" <http://www.chez.com/scribe/wrote:

What is the purpose of using the back button ?

The intended use is to display the previous page as it was previously seen
by the user. You could also prevent this page from being cached browser side
so that it is fetched again from the server (and possibly then updated).

Or perhaps should you implemnt your own link. What is the meaning of using
the back button in your case ?

--
Patrice

<[e-mail] écrit dans le message de groupe de discussion :
[e-mail]...

I use javascript:history.go(-1) to return to the previous page.

I've now found out that when returning to the previous page all
selections that the user made in dropdownlists are lost. How can these
be kept when returning?

I'm very grateful for fast response.

// S- Dölj citerad text -

- Visa citerad text -

The purpose of the back button is to display the previous page as it
was previously seen by the user. How I go back to the previous page
doesn't matter as long as the url isn't changed.

// S

[Stan]

On 15 May, 17:22, [e-mail] wrote:

On 15 Maj, 13:20, "Patrice" <http://www.chez.com/scribe/wrote:

What is the purpose of using the back button ?

The intended use is to display the previous page as it was previously seen
by the user. You could also prevent this page from being cached browser side
so that it is fetched again from the server (and possibly then updated).

Or perhaps should you implemnt your own link. What is the meaning of using
the back button in your case ?

--
Patrice

<[e-mail] écrit dans le message de groupe de discussion :
[e-mail]...

I use javascript:history.go(-1) to return to the previous page.

I've now found out that when returning to the previous page all
selections that the user made in dropdownlists are lost. How can these
be kept when returning?

I'm very grateful for fast response.

// S- Dölj citerad text -

- Visa citerad text -

The purpose of the back button is to display the previous page as it
was previously seen by the user. How I go back to the previous page
doesn't matter as long as the url isn't changed.

// S- Hide quoted text -

- Show quoted text -

There is another approach to this that might be helpful.

Your problem seems to be that you are going away from the first page
when the user initiates a request for the second page. Hence the
browser reloads the first from scratch when you return to it (either
from the local cache or from the server but will make no difference).

Session state can be used to overcome this but an easier solution is
to use a single page with a MultiView control with two Views (one view
for each formerly separate page). That way ViewSate will retain the
content of any web server controls in both views because switching
between then will only occur on postback (but use a postback command
button to do the going back not one that does it via the browser using
JavaScript).

HTH

[staeri]

On 15 Maj, 19:26, Stan <[e-mail]:

On 15 May, 17:22, [e-mail] wrote:

On 15 Maj, 13:20, "Patrice" <http://www.chez.com/scribe/wrote:

What is the purpose of using the back button ?

The intended use is to display the previous page as it was previously seen
by the user. You could also prevent this page from being cached browser side
so that it is fetched again from the server (and possibly then updated).

Or perhaps should you implemnt your own link. What is the meaning of using
the back button in your case ?

--
Patrice

<[e-mail] écrit dans le message de groupe de discussion :
[e-mail]...

I use javascript:history.go(-1) to return to the previous page.

I've now found out that when returning to the previous page all
selections that the user made in dropdownlists are lost. How can these
be kept when returning?

I'm very grateful for fast response.

// S- Dölj citerad text -

- Visa citerad text -

The purpose of the back button is to display the previous page as it
was previously seen by the user. How I go back to the previous page
doesn't matter as long as the url isn't changed.

// S- Hide quoted text -

- Show quoted text -

There is another approach to this that might be helpful.

Your problem seems to be that you are going away from the first page
when the user initiates a request for the second page. Hence the
browser reloads the first from scratch when you return to it (either
from the local cache or from the server but will make no difference).

Session state can be used to overcome this but an easier solution is
to use a single page with a MultiView control with two Views (one view
for each formerly separate page). That way ViewSate will retain the
content of any web server controls in both views because switching
between then will only occur on postback (but use a postback command
button to do the going back not one that does it via the browser using
JavaScript).

HTH- Dölj citerad text -

- Visa citerad text -

Thank you for the suggestion, Stan! Will there be any performance
degradation when using a MultiView? Will both views be loaded
initially or only the first view?

// S