Hi Christofer, I was assuming that this was normal Ajax behavior and understand better now. This would explain that non-Ajax mode would remember the on-change event since the page reload must be getting a new continuation id. I'll certainly take this anomaly with the coolness of Ajax. Thanks, gary
_____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, March 09, 2007 3:20 AM To: [email protected] Subject: AW: Question on Ajax and continuations Hi Gary, Well I think your problem is because of this: When you call sendPageAndWait or showForm cocoon generates a continuation. When doing an on-change action no new Id is generated (al least I havent seen any Server to Client communication indicating this) as soon as you press your browsers back button you get a continuation which lies more in the past than you intended to unfortunately I have no solution for your problem. Maybe just knowing why it doesnt work makes you feel better ;) Regards, Christofer Von: Gary Larsen [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 8. März 2007 15:46 An: [email protected] Betreff: Question on Ajax and continuations I just have a question on Ajax processing to help me understand whats happening. Im using 2.1.9. Heres the scenario: - an on-change listener set values on a form - form is submitted - back button on browser - the values are no longer set When setting values directly on the form the values are still set when returning from the submit. When Ajax is turned off the values also remain set. I dont consider this a real problem considering the benefits of Ajax. Is this normal behavior or could I be doing something wrong? Thanks, gary
