strategies for restoring hidden divs when user clicks back button

[gimme_this_gimme_that]

Depending upon a radio button button's setting a div is either hidden
or visible.

It turns out that the default view of the page requires that the div
be hidden.

When the user opts for the setting that makes the div visible, clicks,
and then clicks the back button the page renders with the div hidden.

I've tried a few strategies to handle this. Adding no-cache meta tags
(not on the server side though and BTW, I'm using JSP), adding a
parameter to the query string on the forwarding page and looking for
it in the request object, looking at the HTTP_REFERRER. Nothing has
worked.

Has anyone run into this issue before and come up with a solution to
this problem?

Thanks.

[David Mark]

On Jul 24, 6:43 pm, "gimme_this_gim me_t...@yahoo.c om"
<gimme_this_gim me_t...@yahoo.c omwrote:

Depending upon a radio button button's setting a div is either hidden
or visible.

It turns out that the default view of the page requires that the div
be hidden.

When the user opts for the setting that makes the div visible, clicks,
and then clicks the back button the page renders with the div hidden.

I've tried a few strategies to handle this. Adding no-cache meta tags
(not on the server side though and BTW, I'm using JSP), adding a
parameter to the query string on the forwarding page and looking for
it in the request object, looking at the HTTP_REFERRER. Nothing has
worked.

Has anyone run into this issue before and come up with a solution to
this problem?

The code that synchronizes the div with the radio button must be run
on page load (onload event.) This is because browsers persist and
restore the states of form elements.

[ASM]

En réponse à gi************* ******@yahoo.co m qui nous a susurré, en date
du : 25/07/07 0:43, le message sibyllin suivant :

Depending upon a radio button button's setting a div is either hidden
or visible.

It turns out that the default view of the page requires that the div
be hidden.

When the user opts for the setting that makes the div visible, clicks,
and then clicks the back button the page renders with the div hidden.

I've tried a few strategies to handle this. Adding no-cache meta tags
(not on the server side though and BTW, I'm using JSP), adding a
parameter to the query string on the forwarding page and looking for
it in the request object, looking at the HTTP_REFERRER. Nothing has
worked.

Has anyone run into this issue before and come up with a solution to
this problem?

back button is to do what ?

to go back, no ?

so, how do you expect, going in past, to get the present ?
of corse, the referrer will not help you, pressing back button you don't
call precedent display's url, you ask the browser to show this one from
its cache.

I do not understand you'd search a server side solution ...

--
Stephane Moriaux et son (moins) vieux Mac

[dhtmlkitchen]

On Jul 24, 3:51 pm, David Mark <dmark.cins...@ gmail.comwrote:

On Jul 24, 6:43 pm, "gimme_this_gim me_t...@yahoo.c om"

<gimme_this_gim me_t...@yahoo.c omwrote:

Depending upon a radio button button's setting a div is either hidden
or visible.

It turns out that the default view of the page requires that the div
be hidden.

When the user opts for the setting that makes the div visible, clicks,
and then clicks the back button the page renders with the div hidden.

I've tried a few strategies to handle this. Adding no-cache meta tags
(not on the server side though and BTW, I'm using JSP), adding a
parameter to the query string on the forwarding page and looking for
it in the request object, looking at the HTTP_REFERRER. Nothing has
worked.

Has anyone run into this issue before and come up with a solution to
this problem?

The code that synchronizes the div with the radio button must be run
on page load (onload event.) This is because browsers persist and
restore the states of form elements.

That is a good solution.

Another possibility would be to use location.hash. This won't work
well with multiple divs, though.

location.hash = '#' + activeDivId;

This is useful when you want to come to the page state from a link,
bookmark, or history, too.