Login Register

Adding to Your Page

To use dojo.back:

  • Define preventBackButtonFix: false in your djConfig like this:.
    <script type="text/javascript"  src="../dojo.js"
        djConfig="preventBackButtonFix: false">

    </script>
    This allows the hidden iframe to be added to the current page via a document.write(). If you do not do this, dojo.back will not work correctly.
  • Add the appropriate require statement:
    dojo.require("dojo.back");

Register the initial state of the page by calling:

dojo.back.setInitialState(state);

This state object will be called when the user clicks Back all the way back to the start of the web application. If the user clicks Back once more, they will go back in the browser to wherever they were before loading the web application.

The state object should have the following functions defined:

  • For receiving Back notifications: back(), backButton() or handle(type), where type will either be the string "back" or "forward".
  • For receiving Forward notifications: forward(), forwardButton() or handle(type), where type will either be the string "back" or "forward".

Example of the a very simple state object:

var state = {
	back: function() { alert("Back was clicked!"); },
	forward: function() { alert("Forward was clicked!"); }
};

To register a state object that represents the result of a user action, use the following call:

dojo.back.addToHistory(state);

To change the URL in the browser's location bar, include a changeUrl property on the state object. If this property is set to true, dojo.back will generate a unique value for the fragment identifier. If it is set to any other value (except undefined, null, 0 or empty string), then that value will be used as the fragment identifier. This will allow users to bookmark the page.

changeUrl is needed to 'go-back' ?? (changeUrl=true works fine)

hi,
I extended my state-object so it splits and stores all params from the url by executing addToHistory. I can 'go back' to previously stored states well whereby all stored params are getting rebuilded for a new request immediately.

If 'changeUrl' is true or a string was set to append as an identiefier for to url, all works fine. But after trying 'changeUrl=false' the back button isn't working no longer.

isn't there a cookie solution?
I would like to hide the identifiers :)

thx for reps!
melchior