Update openpgp_key_id in active account manager UI, if it's changed by a separate UI
Categories
(MailNews Core :: Security: OpenPGP, defect)
Tracking
(Not tracked)
People
(Reporter: KaiE, Unassigned)
References
Details
I recommended to postpone the work on this issue, until after bug 1621128 has landed.
Bug 1621128 introduces code that modifies one of the prefs managed by account manager.
The code in bug 1621128 fully works if the account manager is closed (not shown).
However, if account manager is open, the value set in the other code is lost, and the value still visible in the active account manager "wins".
Detailed steps to reproduce:
- open account manager
- open the "end-to-end encryption" tab, and leave it open
- in addition, use top menu command "tools / openpgp key management"
- in the key manager, use command "generate / new key pair"
- complete that dialog
That will create a new key, with a new key, that appears in addition in the key manager.
The intention is, this new key ID should get saved as the new value for the identity.openpgp_key_id preference.
However, the fact that the account manager is still open seems to override that, and the old value remains.
Desired new behavior:
The "openpgp key manager" should send some kind of event to the open account manager tab, that sends the new value for openpgp_key_id. The account manager code in am-e2e.js should receive that event, and update the value that is shown in the visible dialog element.
|
||
Comment 1•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
|
|
||
Comment 2•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
|
|
||
Comment 3•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
|
|
||
Comment 4•5 years ago
|
||
The severity of these bugs was changed, mistakenly, from normal to S3.
Because these bugs have a priority of --, indicating that they have not been previously triaged, these bugs should be changed to Severity of --.
|
Reporter | |
Comment 5•3 years ago
|
||
Bug 1765974 implemented a fix, the account manager could use an observer to listen for the new broadcast.
Description
•