FS#65551 - Flyspray shows my own username after each comment
Attached to Project:
Arch Linux
Opened by Christian Kujau (ckujau) - Wednesday, 19 February 2020, 01:30 GMT
Last edited by freswa (frederik) - Wednesday, 19 February 2020, 20:29 GMT
Opened by Christian Kujau (ckujau) - Wednesday, 19 February 2020, 01:30 GMT
Last edited by freswa (frederik) - Wednesday, 19 February 2020, 20:29 GMT
|
Details
Description: For some reason the Arch Linux Bugtracker
("Flyspray") writes my own username after every comment made
by other people, and also to the bug's summary ("Opened by"
and "Last edited"). This happens for every bug listed, even
for those that I did not have any interaction with. Of
course, this only happens when I'm actually logged in to
bugs.archlinux.org. Reading my own username after every
comment is kinda distracting and often makes me go "did I
really write this...oh, wait...no, I didn't."
I could not find a UI configuration knob to disable this and could not "reproduce" this on the upstream Flyspray bugtracker, bugs.flyspray.org. I've attached a screenshot to illustrate this for the Arch Linux bugtracker, and another one from Flyspray that does not have this issue. I assume that's just a configuration issue on the Flyspray installation, maybe this can be fixed somehow? |
This task depends upon
Closed by freswa (frederik)
Wednesday, 19 February 2020, 20:29 GMT
Reason for closing: Fixed
Additional comments about closing: PEBCAK
Wednesday, 19 February 2020, 20:29 GMT
Reason for closing: Fixed
Additional comments about closing: PEBCAK
Normally that is where you see the text "- Friday, 14 February 2020, 06:49 GMT-4 — Edit — Delete" or somesuch
Explicitly clearing that field "fixed" this issue and I now see the timestamps after comments and related ticket details. Visiting the settings page again I have to clear my username again from the "Detailed date format" field. The field is defined as:
<input id="dateformat_extended" class="text" name="dateformat_extended" type="text" size="40" maxlength="30" value="">
...and I don't know why this would be pre-filled. But this appears to be related to my Firefox instance, when using another browser the field is not auto-filled. So, sorry for the noise everyone, I'll crawl back under my stone again.