History management

[mikabytes]

For Stone release, we'll only have a means to tell whether or not the browser did "something". There is no way of telling if it went forward, backward, or made a jump.

This is quite limiting.

For this issue:

• Determine strategy for managing the History API. It must be possible to use history the way the web usually does, but it must also be possible to override the standard and always have a predefined "back navigation path", irrespective of what navigation was done previously.
• Implement said strategy.