After we switched to DU4 there were quite a few complaints about how the software change had caused problems with the way people posted.
On DU3, if you were in the middle of a post and you went to a different URL in the same tab to research something, when you clicked "back" then everything you'd written would still be there.
But on DU4 that changed -- when you clicked "back" the text would be gone. It was a pretty big annoyance for some people, but I didn't really have a good handle on why it was happening. Until the changes last week, we were much more integrated into our ad provider's system, so I suspect that the behavior may have been caused by code that they were injecting. Because it wasn't our code, it was a lot more difficult to get a handle on what was going on.
This latest update seems to have resolved that problem, because we've mostly deintegrated from that previous setup -- but unfortunately it's now causing a problem for you, because you prefer the way that it worked previously (ie. page reload when hitting "back" ).
So this is a bit of a tough one, because whatever it was that changed last week fixed an issue that was bothering some people, but has now caused an issue for you. Given that the way it's working now is, generally speaking, the way browsers should work, I'm inclined to leave it as is.
That said, it may be possible for us to include a meta-tag on the Latest page which will prevent caching of that page only -- I'm not sure this is something we should implement site-wide though because that could result in un-fixing the other problem. It would also mean that only the Latest page would reload upon clicking "back." I can look into it, but in the meantime, I wonder if there is a Firefox extension out there that might recreate the behavior you're looking for?
= new reply since forum marked as read