AUR web interface

**This is the bug tracker for the AUR web interface.**

Use this tracker to report bugs or make feature requests regarding the behaviour or implementation of the AUR software.
Please read the Reporting Bug Guidelines before filing a new task.

- Please report bugs related to Arch Linux official packages here:
- Please report bugs for [community] packages here:
- For any packages in the AUR contact the maintainer or leave a comment on the package's detail page.

Source Code:

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
Task Type Bug Report
Category Backend
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 2.0.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


1) Go to a package page (for example
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 
Comment by Karol Błażewicz (karol) - Tuesday, 23 April 2013, 21:41 GMT Comment by Kamil Śliwak (cameel) - Tuesday, 23 April 2013, 22:42 GMT
Sorry for a duplicate. I did look for a similar task before posting but I did not find any. Now I see that I have missed this one on the first page of results. Closed tickets are striked out and this adds a lot of visual noise. My bad.

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.
Comment by canyonknight (canyonknight) - Wednesday, 24 April 2013, 22:40 GMT
I agree that it could definitely be improved and would say that through the use of the PRG pattern as was suggested with  FS#31882  it 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.