Re: How do I get a page to maintain control states?
From: Tom wilson (yeahright_at_nospam.com)
Date: 02/16/05
- Next message: tshad: "Re: Giving Focus on PostBack"
- Previous message: Norman: "DHTML Date Picker Recommendations"
- In reply to: Patrice: "Re: How do I get a page to maintain control states?"
- Next in thread: Chad Devine: "Re: How do I get a page to maintain control states?"
- Reply: Chad Devine: "Re: How do I get a page to maintain control states?"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 16 Feb 2005 15:05:00 -0500
">- if something is wrong I would redisplay the whole form with the
error message so that the user doesn't even have to use the back
button."
That sounds logical, doesn't it? My main app works this way. You get
your form, fill stuff out and submit. The page returns to the browser
with red error texts above each 'errored' control. Its a work of art.
You can submit repeatedly until all errors disappear. I'm proud.
But click back anywhere during this process, even after 5 submits, the
page is returned blank. Come on, you know SOMEbody is going to click
the back button and call me up, pissed.
So I tried your time example as suggested below:
- Load form. Time is: 2:53:12
- Enter text, submit
- Time is 2:53:33
- Click "Back"
- Time is: 2:53:12
I assume the page is coming from IE's cache cause the time is the same
when going back. If it came from the server the time would be past
2:53:33, right?
So this means... asp.net pages are not capable of maintaining state?
:)
Or that IE is somehow killing the page state when it reloads the page
from its cache?
Nothing is making any sense.
(thx for the reply!)
On Wed, 16 Feb 2005 20:27:11 +0100, "Patrice" <nobody@nowhere.com>
wrote:
>I don't see what difference you make between point 1 to 4 and the later
>scenario (not clear if you used submit before using the back button).
>
>IMO :
>- if something is wrong I would redisplay the whole form with the error
>message so that the user doesn't even have to use the back button. Keep in
>mind that you would rely here on a client side behavior that the user could
>have altered (by changing its IE settings).
>
>- for now I have the behavior you described in point 1 to 4. Could it be a
>problem with your cache ? I would try to add a date/time information to the
>page to see if the page with blank fields comes from the IE cache or if IE
>gets it once again from the server. It could be also a IE settings. For now
>it looks liike that when you using the back button, IE gets the page again
>(AFAIK it was also the behavior on old IE releases, whcih version are you
>using).
>
>Good luck.
>
>Patrice
- Next message: tshad: "Re: Giving Focus on PostBack"
- Previous message: Norman: "DHTML Date Picker Recommendations"
- In reply to: Patrice: "Re: How do I get a page to maintain control states?"
- Next in thread: Chad Devine: "Re: How do I get a page to maintain control states?"
- Reply: Chad Devine: "Re: How do I get a page to maintain control states?"
- Messages sorted by: [ date ] [ thread ]