invalid certificate triggers more than 94 "add security exception" dialog windows for the same calendar site
Categories
(Calendar :: General, defect)
Tracking
(Not tracked)
People
(Reporter: akrupp.gh, Unassigned)
References
Details
Attachments
(1 file)
|
111.66 KB,
image/png
|
Details |
Steps to reproduce:
Left Thunderbird open and running on a 24/7 system for a couple of days. Did not update a calendar site SSL certificate which became invalid yesterday.
Actual results:
Thunderbird opened more than 94 "Add Security Exception" dialogs, all for the same site. Cf. attached screenshot.
In other cases I could press and hold ESC until they were all gone, but in this case a sequence of Alt-Tab, ESC was required. I chose to kill Thunderbird instead.
Expected results:
From a UX perspective a single dialog open at any time for a single site should be sufficient to notify the user about a site problem.
Almost 100 application-modal dialogs open at any one time cannot be a feature.
Updated•3 years ago
|
Comment 2•2 years ago
|
||
I experienced something like this on my laptop yesterday. On this device, I have Thunderbird configured to connect to multiple CalDAV calendars. I travelled with the laptop and connected to a public WiFi network with a captive portal, which I assume uses DNS hijacking to redirect HTTP requests to its login portal. Probably as a result of this DNS hijacking, Thunderbird immediately threw up a very large number of Add Security Exception dialogs for my calendars. I had to individually dismiss them in the correct order (which isn't the same order they were stacked by my window manager), which was very inconvenient and time-consuming.
Thunderbird probably did the right thing in warning me about the certificate errors, but it shouldn't have done this through individual modal dialogs. A single modal dialog that lists all the certificate errors would be better.
Yes, a captive portal is one of the triggers for the behaviour, as per my original description. Thanks for the report.
version bump. still occurs on 115 esr.
Comment 5•2 years ago
|
||
IIRC it's preferred to keep the version field set to the earliest version the bug is known to affect.
As long as this does not affect the chances of this being picked up - 115 is a current ESR, at least...
Description
•