[Seaside] Enable Browser Back Button with AJAX-Scriptaculous

[Boris Popov]

That's the one of a few key reasons YUI Browser History Manager exists,

http://developer.yahoo.com/yui/history/

Quote: Client-side changes to a web page's content and structure are not
recorded by the browser's history engine. As a consequence, the
navigation buttons (back/forward) we've learned to use as we traverse
the World Wide Web of documents don't usually serve us well when we
begin exploring the World Wide Web of applications. Bookmarking, too, is
problematic in web applications, as the application can change state
hundreds of times through the course of a session without any change to
the original document's URL. These are significant problems in the
current paradigm of web application development.

-Boris

-- 
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

boris at deepcovelabs.com

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of dirk newbold
> Sent: Friday, August 31, 2007 3:53 PM
> To: Seaside - general discussion
> Subject: [Seaside] Enable Browser Back Button with AJAX-Scriptaculous
> 
> Hi All - Newbie Question,
> 
> I've the classic Header, Fixed Left & Right Sidebar with Liquid Center
and
> Footer which I had originally developed without Sciptaculous.
> 
> Upon learning Scriptaculous I've redeveloped the entire site with AJAX
so
> that the Header, Two Side Bars and Footer are not continually
rerendered,
> but I've just realised that the browser's back button is now rendered
> useless as the url stays constant.
> 
> How do I get the url to act as before so that the user can scroll back
> through their past nav using their browsers back button?  Navigation
> through the site has been achieved through the use of onClick: (html
> updater id: 'xxx'; callback: [ ]), so if that is the wrong approach
please
> let me know.
> 
> Sorry if this has been posted previously but my seaside vocab wasn't
> accurate enough.
> 
> Cheers,
> 
> Dirk
>