window.location.hash = 'action=test'; The onhashchange even doesn't fire.
This is a good thing, because it means you can set up an initial hash representing the AJAX state. However the back button would take you from
http://example.com/#action=test to http://example.com/
Which creates a usability problem as the back button then has to be pressed twice to actually go back.
SOMEHOW Google manage to avoid this. To see, open docs.google.com in a new window or tab and you will be taken to http://docs.google.com/#all
And yet the back button is disabled - as if the transition to #all never even happened.
Does anybody know how they do this? As it would solve the double back button problem I mentioned above.
(This doesn't appear to be a serverside redirect as the hash appears once the page has loaded).