No he means that say he had page A and on there had a update button for
example and pressed it 3 times, thats 3 postbacks.
When he presses back he has to press back 4 times (to get past the 3
postbacks) in order to get to the original page.
I actually have the same annoying problem, i am sure there is a workaround,
their must be. I think the smartnav directive may solve it (tho it is not
crossbrowser but i think some peopl ehave made their own that is) or you
could make your own back button and store the original page that started the
chain as the target, combine that with the javascript from the previous post
and they will have to use your back button.
--
Dan
"Naveen K Kohli" <na*********@hotmail.com> wrote in message
news:OY**************@TK2MSFTNGP10.phx.gbl...
IF you don't want user to access the page by BACK button, then best would
be to disable CACHING of pages by client browser by adding prope meta tags
on pages. You can try the following JS on each page and it should disable
ability to use BACK button.
<script language="javascript">
window.history.forward(1);
</script>
"Shimon Sim" <sh**********@community.nospam> wrote in message
news:e4***************@TK2MSFTNGP12.phx.gbl... Hi
Is it possible to make sure that the page doesn't show in browser history
and won't effect Back button.
The problem is that every postback shows as another entry for "Back"
button and user goes through the hole history of postbacks if she wants
to get to previous page.
Thank you,
Shimon