i've had this same problem. unfortunately, i've never been able to find a fix for it - using the "back" button seems to break the intended functionality of the datascroller, and it always reverts back to page 1.
interestingly enough, you can see the same behavior on the "usage" tab of the datascroller demo page, although the "scroller facets usage" tab seems to behave in the desired fashion. sadly, binding the "page" attribute of the datascroller seems to have no effect on this issue for me.
additionally, when using an extendedDataTable, any sorting that has been done reverts back to the default as well.
the workaround that i have done is use something along the lines of:
<body onload="reloadContent()"> ... </body>
in conjunction with:
<a4j:jsFunction name="reloadContent" reRender="panel_to_refresh_name" />
on any page that uses a table with a datascroller.
i would LOVE to find a solution to this problem, as there are cases in my application where reloading the page takes alot of time.
Browser didn't care about ajax requests which was between loading the page and pressing the Back button. And RichFaces has no functionality to control this. Try to check for some thirdparty.