Issue500

Title Posting changes from "old" tracker pages causes spurious updates
Priority bug Status chatting
Superseder Nosy List ezio.melotti, stephen
Assigned To Topics

Created on 2013-01-04.03:18:27 by stephen, last changed 2013-01-06.00:11:08 by ezio.melotti.

Messages
msg2681 (view) Author: stephen Date: 2013-01-04.03:18:27
See also thread starting at http://mail.python.org/pipermail/python-dev/2013-January/123437.html.

Jesus Cea writes:

I get the notification about new issues open in the bugtracker. If I 
see an interesting "bug", I usually open a Firefox tab with it, to 
monitor it, decide if I will work on it in the future, whatever. 
 
When I have time to decide, I proceed. If I find the issue interesting 
but don't have the time to work on it, or somebody else is taking care 
of it, I just add myself to the nosy list, and close the tab. 
 
The problem with this is that even if I reload the tab, flags are 
usually stale and when I add myself to the nosy list, I revert flags 
to the old value.
msg2682 (view) Author: ezio.melotti Date: 2013-01-06.00:11:07
> The problem with this is that even if I reload the tab, flags are 
> usually stale and when I add myself to the nosy list, I revert flags 
> to the old value.

Preserving form data on reload is a browser feature.
The solution is either to reload with CTRL+F5 or opening the page again (this can also be done with CTRL+L, Enter).  Both will update the form with the most recent data, discarding anything you might have changed/added.
The CTRL+L, Enter can also be used when Roundup displays a red bar about a conflict.  In that case CTRL+F5 might resend the POST data and cause the conflict again.  Opening the page on a new tab also works.

I don't think there's anything more Roundup should do.  (Maybe something can be done, but I'm not sure it's worth to fix this specific "problem".)
History
Date User Action Args
2013-01-06 00:11:08ezio.melottisetstatus: unread -> chatting
nosy: + ezio.melotti
messages: + msg2682
2013-01-04 03:18:27stephencreate