I have some XSL templates that include various filters handled with javascript and they work fine so long as the users stick to the menus/features provided in the XSL. However, if they hit the Back/Forward buttons on the browser, then my code seems to 'lose its way' and dies: The display is still there but the buttons are inactive.

So my question is whether I can protect myself from this? Or if I can force the javascript to 'come back from the dead' without getting the user to close and re-open the browser.

Or maybe there is a HOWTO on this point?

Many thanks,
Alan Searle.