Event handlers linger if Exchange credentials dialog is shown twice in one session
Categories
(Thunderbird :: Account Manager, defect, P2)
Tracking
(thunderbird_esr91+ fixed, thunderbird92+ fixed)
People
(Reporter: neil, Assigned: aleca)
References
(Regression)
Details
Attachments
(1 file, 1 obsolete file)
(deleted),
text/x-phabricator-request
|
wsmwk
:
approval-comm-beta+
wsmwk
:
approval-comm-esr91+
|
Details |
The code to prompt the user to log in to their Exchange autodiscover server does not uninstall all, or in some cases, any, of its event handlers. This results in outdated event handlers lingering which might interfere with a potential reuse of the dialog in the same session. A typical reason why the dialog would be reused is if the autodiscover server needs the username in domain\user format, in which case the initial login would fail and the user would be prompted to send the new credentials to the autodiscover server.
Reporter | ||
Comment 1•3 years ago
|
||
Using event handler properties seemed to be the easiest way to ensure that only the current event handlers are active, but I'm open to other approaches.
Updated•3 years ago
|
Updated•3 years ago
|
Assignee | ||
Comment 2•3 years ago
|
||
Ah, good find.
The { once: true }
attribute of the addEventListener()
method only removes the event if the button is actually clicked, but if the user dismisses the dialog, more click events will probably be stacked upon reopening.
I'm okay with this solution, but maybe we could remove the event listener when the dialog is closed.
This is most likely a code styling decision.
Pinging Magnus to see which one he thinks we should adopt.
And we should also do the same for the _showCalendarDialog()
method.
Comment 3•3 years ago
|
||
The patch seems like maybe the best solution to me.
Assignee | ||
Comment 4•3 years ago
|
||
Assignee | ||
Comment 5•3 years ago
|
||
Assignee | ||
Comment 6•3 years ago
|
||
Apologies Neil for taking over this bug.
This issue is fairly important so I wanted to fix it as soon as possible.
Updated•3 years ago
|
Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/fcf8c3d07382
Use onclick instead of event listeners in account setup tab to prevent lingering handlers. r=mkmelin
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 8•3 years ago
|
||
Comment on attachment 9236243 [details]
Bug 1724940 - Use onclick instead of event listeners in account setup tab to prevent lingering handlers. r=mkmelin
[Approval Request Comment]
Regression caused by (bug #): -
User impact if declined: Issues with the dialog buttons when setting up an exchange account or multiple calendars
Testing completed (on c-c, etc.): on c-c
Risk to taking this patch (and alternatives if risky): low
Assignee | ||
Comment 9•3 years ago
|
||
Comment on attachment 9236243 [details]
Bug 1724940 - Use onclick instead of event listeners in account setup tab to prevent lingering handlers. r=mkmelin
[Approval Request Comment]
Regression caused by (bug #): -
User impact if declined: Issues with the dialog buttons when setting up an exchange account or multiple calendars
Testing completed (on c-c, etc.): onc-c
Risk to taking this patch (and alternatives if risky): low
Comment 10•3 years ago
|
||
Comment on attachment 9236243 [details]
Bug 1724940 - Use onclick instead of event listeners in account setup tab to prevent lingering handlers. r=mkmelin
[Triage Comment]
Approved for beta
Comment 11•3 years ago
|
||
We're building 91.0.2 today, but this hasn't yet been on beta. So this will be eligible for 91.0.3 which will probably happen next week.
Comment 12•3 years ago
|
||
bugherder uplift |
Thunderbird 92.0b3:
https://hg.mozilla.org/releases/comm-beta/rev/a996ef6a0cd4
Comment 13•3 years ago
|
||
Comment on attachment 9236243 [details]
Bug 1724940 - Use onclick instead of event listeners in account setup tab to prevent lingering handlers. r=mkmelin
[Triage Comment]
Approved for esr91
Comment 14•3 years ago
|
||
bugherder uplift |
Thunderbird 91.0.3:
https://hg.mozilla.org/releases/comm-esr91/rev/1b5a88b5461d
Reporter | ||
Comment 15•3 years ago
|
||
(In reply to Alessandro Castellani from comment #6)
Apologies Neil for taking over this bug.
This issue is fairly important so I wanted to fix it as soon as possible.
No need to apologise, I simply haven't been responsive because I've been recovering from an emergency operation.
Description
•