Re:Why not a 'tree' back button? (Score 1)

Your concept is similar to what I have been thinking, but the implementation is not exactly the same. I think that we shouldn't get rid of Back and Forward, but instead add a third button called Path which will allow one to traverse the history in completely nonlinear fashion. Pressing the button at any point would review a tree of exactly how the user has navigated from each page. Example: Page A
===>Page B
=====>Page C
===>Page D
=====>Page E
Page F
===>Page D
=====>Page A
========>Page G

Thus, from any point in the session, the user can choose to revist the page he wants, no matter where in the history he is currently at.

Mouse gestures are not necessary and will only confuse people

One more thing: Why doesn't /. allow <pre> tags? Shouldn't be a problem if you close 'em...