FS#34896 - Refreshing package page after posting a comment posts it again
Attached to Project:
AUR web interface
Opened by Kamil Śliwak (cameel) - Monday, 22 April 2013, 23:52 GMT
Last edited by canyonknight (canyonknight) - Wednesday, 24 April 2013, 22:41 GMT
Opened by Kamil Śliwak (cameel) - Monday, 22 April 2013, 23:52 GMT
Last edited by canyonknight (canyonknight) - Wednesday, 24 April 2013, 22:41 GMT
|
Details
1) Go to a package page (for example
https://aur.archlinux.org/packages/libdrm-git)
2) Write your comment in the 'Add comment' box. 3) Click 'Add comment'. The comment gets posted. 4) Refresh the page with F5. The comment gets posted again. 5) Refresh the page with F5. The comment gets posted again. 6) Refresh the page with F5. The comment gets posted again. 7) ??? 8) Profit. |
This task depends upon
Closed by canyonknight (canyonknight)
Wednesday, 24 April 2013, 22:41 GMT
Reason for closing: Duplicate
Additional comments about closing: See FS#31882
Wednesday, 24 April 2013, 22:41 GMT
Reason for closing: Duplicate
Additional comments about closing: See
Regarding the comments in that other ticket (I'd post there but it's closed), I think that while it's Opera's fault that it does not ask me whether I actually want to resubmit my comment (I have just checked and both Firefox and Chrome do ask in the same situation), I can hardly imagine a situation in which I would want to resubmit it after a successful submission. It's natural to expect F5 to just issue a GET request and fetch a newer version of the page. That way I can see if possibly someone has responded. You could easily achieve this by using a redirect rather than rendering the page directly as a response to the POST request.
Also, if you have multiple package pages open in separate tabs (some possibly more than once - it happens sometimes if you open links in new tabs for later) and you have commented on some of them, you cannot easily discern the ones where you can safely hit F5 from the ones where you cannot. User is forced to think about it instead of having a hassle-free experience.
It's not a big deal and not high priority but I can see some room for improvement here.
FS#31882it would work as you expect. As you said it isn't exactly a high priority and it could be a long while before it is changed.