I am relatively new to AJAX design patterns. I have a grid which usually shows multiple pages, as a simple publication catalog.
Let's say the user navigates to page 5 using the standard control, and then clicks a templated column entry that contains a hyperlink to a publication detail page.
Using the browser's Back button returns to the same grid, same data, but resets to showing the first page of results. I think this is expected because the paging is done on the client and disappears once the page is left via the hyperlink.
I have set the scroll bars for the grid, and enabled maintain position options, so if I return to the page, the proper grid page is displayed.
So, is there a way to get these in sync? Note that I have set a fixed client scrolling size, enabled saving of viewstate, etc.
As a test, I have set the selected page index as an IIS session variable, and then reset the grid upon return, but this seems like a NON-best practice, if you know what I mean.
Also note that my question is not at all related to browser history with the Back button, as far as I can tell, that has no relevance here.
Let's say the user navigates to page 5 using the standard control, and then clicks a templated column entry that contains a hyperlink to a publication detail page.
Using the browser's Back button returns to the same grid, same data, but resets to showing the first page of results. I think this is expected because the paging is done on the client and disappears once the page is left via the hyperlink.
I have set the scroll bars for the grid, and enabled maintain position options, so if I return to the page, the proper grid page is displayed.
So, is there a way to get these in sync? Note that I have set a fixed client scrolling size, enabled saving of viewstate, etc.
As a test, I have set the selected page index as an IIS session variable, and then reset the grid upon return, but this seems like a NON-best practice, if you know what I mean.
Also note that my question is not at all related to browser history with the Back button, as far as I can tell, that has no relevance here.