After doing some digging it turns out this seems to be a pretty common issue with IE and Ajax pages.
There are numerous plug-ins for jQuery and etc. to work around the problems when using IE with Ajaxified pages - most using window hashcode calls.
It would be awesome to see one of the various plug-ins baked into Nop Ajax Filters as it would solve the IE issue and could also make things better in other browsers.
A quick Google search on 'ie back button ajax' will return 1,030,000 results on the topic and it's easy to go from there...
This would be an awesome improvement to Nop Ajax Filters.
We are seeing an issue when a user makes filtering choices and then goes to the item detail page and then uses the browser back button to return to the grid view.
If using Firefox, the browser back button takes the user back to the previous page and the filter selections and items shown are as expected. (Works Properly)
If using IE, the browser back button takes the user back to the previous page and the filter selections are all reset and the items shown are reset.
Any way to resolve this IE specific issue?
In a perfect world, both Nop and the Nop Ajax Filters plug-in would use a cookie or something to keep track of the user's sort order, items per page and all the various filtering selections made so they all remained 'sticky' for the user not only from page to page but also across logins (as an optional setting). Maybe someday.
For now, If we could at least get IE to not blow away the filtering selections just from the back button, it would be a step ahead.