Closed Bug 1717307 Opened 2 years ago Closed 9 months ago

Activity Manager Time Stamp for Failed Connection

Categories

(Thunderbird :: Mail Window Front End, defect)

defect

Tracking

(thunderbird_esr102 unaffected)

RESOLVED FIXED
93 Branch
Tracking Status
thunderbird_esr102 --- unaffected

People

(Reporter: tonydi.499, Unassigned)

References

Details

(Whiteboard: [fixed by bug 1683865])

Attachments

(1 file)

Attached image Capture.PNG

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:89.0) Gecko/20100101 Firefox/89.0

Expected results:

All of the activities in the Activity Manager have time stamps except "Failed to connect to server".

Since those activities all pile up at the top of the window, you can't even use the other activity time stamps to approximate when the failures occurred.

The Failed to connect to server activity needs a time stamp.

I can confirm the bug.

Is this an easy fix?

Status: UNCONFIRMED → NEW
Component: Untriaged → Mail Window Front End
Ever confirmed: true
Flags: needinfo?(bugzilla2007)
See Also: → 516523

Does anyone know why error messages in the Activities Window do not have a timestamp? All other messages in the Activities Window have a timestamp, but the important error messages do not. So you can't solve errors if there is not even a timestamp. Too bad.

This went broken by de-XBL in bug 1530300 and was fixed again in bug 1683865 comment #119, 2021-08-13 during TB 93:
https://hg.mozilla.org/comm-central/rev/6fabadfb4f73220a218c1848afbb75b1415f1a0e

Fix for TB 91:
https://github.com/Betterbird/thunderbird-patches/blob/main/91/bugs/1717307-alert-activities-time-stamp.patch
Mostly a typo. This shows that the de-XBL changes weren't fully tested.

FIXED by bug 1683865 (bug 1683865 comment #119, 2021-08-13 during TB 93).

Status: NEW → RESOLVED
Type: enhancement → defect
Closed: 9 months ago
Flags: needinfo?(bugzilla2007)
Resolution: --- → FIXED
Target Milestone: --- → 93 Branch
Whiteboard: [fixed by bug 1683865]
You need to log in before you can comment on or make changes to this bug.