OBSOLETE?

Back Button Patterns

This (work in progress) wiki page is about patterns and examples for effectively using the history tracking features of dojo.io.bind. The dojo.io.bind library allows JavaScript web programmers to set Back Button and Forward Button callbacks. This wiki page is for debate, discussion, and documentation on how to use these callbacks effectively for various use cases...

Form Anti-Pattern

When using dojo.io.bind in a simple form, such as for auto-completing fields, you probably don't need to use the history callbacks. Users will likely expect the Back button to return them to the page that has the link that launches the form, not to some intra-form editing state.

Wizard Dialog Patterns

A wizard is a series of dialog pages with Next and Previous buttons to collect information from the user. Think of the classic Windows software Setup/Installer UI. Or the Checkout pages in a retail web site. How do we use the Back button feature here?

• The Back button takes you to the same page as the Previous button.
  • The Forward button, in turn, is almost same as the Next button (only if you hit the Back button, of course). And, the Forward button might lost any edits that the user made.
• The Back button takes you to the first page in the Wizard.
• The Back button takes you to the page that links to the Wizard.

Tabbed Panel Pattern

How do we use the back button feature here?

Here's an article from Jakob Nielsen that contains some insights on tabs: http://www.useit.com/alertbox/991114.html
The topic is addressed as a part of his discussion (rant) on the misuse of tabs as a navigational element. But Nielsen's conclusion is a good one: "Tabs are supposed to be used for rapid switching between alternative views of the same information object. It would be very appropriate to use tabs to switch between the alternatives while retaining the main context and illusion of being at a single location on the site."

From this, the key point is that tabs are local alternative views of the same object. This means that tabs should not add another entry to the back button history, and the back button should return users to the previous (actual) page.

Shopping Cart Pattern

How do we use the back button feature here?

Tree Navigator Panel Pattern

Think of a file manager or Mozilla's preferences dialog. The left-hand-side of the window has a hierarchy of items. The right-hand-side panel of the window changes depending on what is selected on the left-hand-side hierarchy.

• The Back button takes you to the previous visited element.
  • The Forward button, in turn, takes you to the next visited element (if any).
• The Back button takes you to the parent node.
  • The Forward button, in turn, takes you to the first child of the current node, if any, otherwise to the next sibling,  if any, otherwise to the next parent sibling (the tree view updates as to reflect the position, by opening trees subsquently).
• The Back button takes you to the page that links to the tree (especially when on the first visited element or the root element).

http://glazkov.com/blog/archive/2005/03/27/406.aspx -- The Curse Of The Back Button

-- initiated by SteveYen?