Hmmm, but your code uses javascript, what I want to achieve is a back button support even if the browser has javascript disabled.
I appreciate your response, thanks for your help ;) Any other ideas here? -----Original Message----- From: Luka Surija [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 25, 2007 12:24 AM To: MyFaces Discussion Subject: Re: How to support back-button with either Javascript turn-off or on in the browser <body onload="window.history.forward(1);"> works for me Luka Bryan Sevilla wrote: > > Any help pls... > > -----Original Message----- > *From:* Bryan Sevilla > *Sent**:* Saturday, September 22, 2007 10:43 AM > *To:* '[email protected]' > *Subject:* How to support back-button with either Javascript turn-off > or on in the browser > > I'm having problem on providing back-button (browser backbutton) > support for browsers having javascript both turn-off or on. Can > anybody guide me on how can I achieve this using myfaces 1.1.5 and > tomahawk-1.1.5? > > I've look into the source, and I've noticed that for server-side state > saving, you're caching the SerializedView of the current request in > the session, and you're retrieving it using the current request ViewId > and jsf_sequence. All of this needed keys to retrieve the restore the > view from the session were wrapped into the javax.faces.ViewState > stored somewhere else. To properly restore the View from the session, > I've just think I may need that javax.faces.ViewState in my request > both GET and POST. Can you someone pls. clarify if my idea is correct? > and how could I implement this using myfaces? Or maybe myfaces has > already provide this behavior i've been thinking of, how could I > configure this with myfaces? > > I've resorted to server-side thing solution as the ViewState of > client-side state saving is too large to append it on GET request params. > > Thanks, > > Bryan >
