Clicking the "continue" button in the import secret key dialog before selecting a file causes: Uncaught (in promise) TypeError: can't access property "length", gFiles is undefined
Categories
(MailNews Core :: Security: OpenPGP, defect)
Tracking
(thunderbird_esr78+ wontfix, thunderbird86+ affected)
People
(Reporter: lasana, Assigned: lasana)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file, 2 obsolete files)
|
1.22 KB,
patch
|
aleca
:
review+
|
Details | Diff | Splinter Review |
The continue button should be disabled until the user has actually selected a key.
| Assignee | ||
Comment 1•4 years ago
|
||
Make the continue button disabled by default.
| Assignee | ||
Updated•4 years ago
|
Comment 2•4 years ago
|
||
This happens only if using the menu item "Import secret keys from file" fro the OpenPGP Key Manager.
Comment 3•4 years ago
•
|
||
Updated•4 years ago
|
| Assignee | ||
Comment 4•4 years ago
|
||
I disable the button closer to the code that displays this specific section.
| Assignee | ||
Comment 5•4 years ago
|
||
Question: Is the plan to eventually remove the key manager from the main menu? Currently it's a little inconsistent, clicking back on this same "import secret key" screen takes you to the section used in the account settings rather than the key manager dialog.
Comment 6•4 years ago
|
||
(In reply to Lasana Murray from comment #5)
Question: Is the plan to eventually remove the key manager from the main menu? Currently it's a little inconsistent, clicking back on this same "import secret key" screen takes you to the section used in the account settings rather than the key manager dialog.
Indeed, we have bug 1662282 for it.
The plan is, most likely, to move this whole key manager into a tab.
Comment 7•4 years ago
|
||
| Assignee | ||
Comment 8•4 years ago
|
||
Disabling the button on init() only when the code is directly requesting the
import section makes more sense.
Just a thought on this:
Wouldn't it be more idiomatic to have the accept button disabled by default and only enable it when the conditions for "continuing" are satisfied?
| Assignee | ||
Comment 9•4 years ago
•
|
||
Move the change to the init function.
Comment 10•4 years ago
|
||
Wouldn't it be more idiomatic to have the accept button disabled by default and only enable it when the conditions for "continuing" are satisfied?
Sure, I'm okay with that.
Up to you if you want to take on the burden of updating the dialog, which is currently used by both the e2ee page as a subdialog and by the Key Manager as a regular dialog.
That's why there are some strange approaches and timeouts in it, in order to be able to use the same source in both scenarios.
Comment 11•4 years ago
|
||
| Assignee | ||
Updated•4 years ago
|
Comment 12•4 years ago
|
||
Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/75a28605a427
Disable continue button by default when importing secret keys via the key manager. r=aleca
Comment 13•4 years ago
|
||
Maybe not worth uplifting.
Description
•