Ajax updates not 'sticky' with Back/Forward or Tab Reload

[John A Meinel]

I don't remember the exact permutation of how I triggered this, but it was either a Close Tab, Ctrl+Shift+T (reload the closed tab), or navigate away and then hit Back.

Anyway, the new Ajax edit-in-place are quite pretty, and certainly give a nice interactive feel. However a few times now I've done an edit, and then when I come back to the page in my browser history, it looks like I haven't my the change. I have to force-reload the page with Ctrl+R.

My guess is that Firefox caches the initial page when viewed, but doesn't remember any Ajax updates. I sort of understand why it does this but it is confusing. (I was just on the page, with it showing the right thing, I go to the next, and go back, and suddenly the page is wrong?)

Is it possible to have the inline ajax updates flag the page cache as out-of-date so that Firefox knows it needs to reload the page rather than trust its cache?

[John A Meinel (jameinel)]

Steps to reproduce:

1) Go to a bug
2) Mark it as a duplicate
3) Follow the new link to the target dup bug
4) Hit Back
5) The "Mark this bug as a Duplicate" link is back
6) Hit Reload, the "This bug is a duplicate of XXXX" is now shown correctly.