Well, IE actually does refresh the page in certain situations, I've seen. Firefox doesn't have this problem at least in my experience.
On Thu, Jun 26, 2008 at 12:00 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > this has nothing to do with versioning. when you press the back button > in the browser there shouldnt even be a hit to the serverside, the > browser simply pulls what it thinks the last page is out of its cache. > > -igor > > On Thu, Jun 26, 2008 at 12:36 AM, Benny Weingarten > <[EMAIL PROTECTED]> wrote: >> >> I am fronting a similar problem. My users don't refresh, they go back and >> forward using the browser's back and forward buttons. >> >> In my wicket application, I have a FeedbackPanel in my page that displays >> error or success, depending on whether the form submitted successfully or >> not. My Form is a personal information edit form, in which a user can change >> information about themselves (such as name, interests, hobbies, etc`..) >> >> Lets say a user does the following in the form: >> 1) changes a hobby, submit the form (success). A success message is >> idsplayed via the FeedbackPanel >> 2) blanks the name field, submit the form (failure. In wicket terms, the >> validation failed on the TexfField Model object, and the Form's onError >> method was called) an error message displayed via the Feedback Panel >> 3) changes the name field to a valid name, then submit. (success). A >> success message is displayed via the FeedbackPanel >> >> At this point, if the user clicks on the browser's back button, I would >> expect the form to be visible with the erroneous "name" field, and the error >> message. However, the form is displayed with the value entered at (3), >> without any error message. >> >> User clicks back again and I would expect the form to display the new hobby >> field, with the success message from (1). What I see is the same page as >> after (3), with no feedback message. >> >> Its as if once I submit the form, the previous values of the form are not >> retained. I am calling setVersioned(true) on the form, and according to the >> docuumentation that should make the form retian previous states, but it >> doesn't seem to work. >> Suggestions? >> >> >> SantiagoA wrote: >>> >>> feedbackMessages are stored to show them once, aftewards they were >>> deleted. Perhaps, try to store them in your own List and feed the >>> FeedbackPanel with the List when the page is displayed again. Maybe this >>> work, i´m not sure about that. ;-) >>> >>> -Santiago >>> >>> >>> Thomas Lutz wrote: >>>> >>>> Hi, >>>> >>>> First of all, great framework ! >>>> >>>> I've a form with some validation added, nothing special (Required, Email >>>> check). When I submit the form I get the validation messages in the >>>> FeedbackPanel as expected, but :-), hitting f5 for a page refresh after >>>> the submit removes them (don't ask why refresh after submit... users of >>>> my webapp do stuff like this :-)). >>>> The form is not submitted, only redisplayed, but the validation messages >>>> are missing. >>>> Is there something I can do about this ? >>>> >>>> Thanks in advance, >>>> Tom >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>>> >>>> >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/FeedbackPanel-and-page-refresh-%28f5%29-after-submit-tp14413642p18128149.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
