account provisioner doesn't handle utf-8 account configuration data
Categories
(Thunderbird :: Account Manager, defect)
Tracking
(thunderbird_esr78+ fixed, thunderbird87+ fixed)
People
(Reporter: mkmelin, Assigned: mkmelin)
Details
Attachments
(3 files)
1.27 KB,
patch
|
aleca
:
review+
|
Details | Diff | Splinter Review |
2.11 KB,
patch
|
aleca
:
review+
|
Details | Diff | Splinter Review |
12.79 KB,
patch
|
aleca
:
review+
wsmwk
:
approval-comm-beta+
wsmwk
:
approval-comm-esr78+
|
Details | Diff | Splinter Review |
The account provisioner doesn't handle UTF-8 data in the configuration data.
There's also a few other minor fixes I'll attach to this bug.
Assignee | ||
Comment 1•4 years ago
|
||
Just cleanup to avoid unwarranted errors in the console. Doesn't change anything.
Assignee | ||
Comment 2•4 years ago
|
||
I'm not sure exactly what's wrong with these as is. After setup there were (sometimes?) errors that "gMessageListeners[index].onStartHeaders is not a function". After I changed to for..of I don't see it, and it's easier to read this way.
Assignee | ||
Comment 3•4 years ago
|
||
UTF-8 e.g. in the password set by the provider was not working.
Some other buggy things cleared up as well:
- outgoing password was incorrectly set to incoming password
- config.password isn't a thing
- added a test for the successful account setup case which strangely doesn't seem like it was tested even if the unsuccessful cases were thoroughly tested.
Comment 4•4 years ago
|
||
Comment 5•4 years ago
|
||
Comment 6•4 years ago
|
||
Assignee | ||
Comment 7•4 years ago
|
||
(In reply to Alessandro Castellani (:aleca) from comment #6)
Would we need to let the providers we have know that we're changing the XML
config?
I' only changed test data here. The test data was changed to read "imap-provisioned" because imap was hard to find, and the other test case threw me off for a while.
displayShortName is not used anywhere (by our code).
Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/c241aae62d26
ignore responses that don't have contentType set (like for OPTIONS). r=aleca
https://hg.mozilla.org/comm-central/rev/1552e6e26e18
use for .. of loops for gMessageListeners. r=aleca
https://hg.mozilla.org/comm-central/rev/92ace0642be5
account provisioner doesn't handle utf-8 account configuration data. r=aleca
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 9•4 years ago
|
||
Comment on attachment 9204290 [details] [diff] [review]
bug1693883_utf8_provisioner.patch
[Approval Request Comment]
User impact if declined: can end up with bad account configuration through account provisioner (mainly if using non-ascii in password), and for one of the cases: missing header pane for first account of profile, until restart.
Testing completed (on c-c, etc.): on c-c
Risk to taking this patch (and alternatives if risky): not too risky, adds a test
All three changesets.
Comment 10•4 years ago
|
||
Comment on attachment 9204290 [details] [diff] [review]
bug1693883_utf8_provisioner.patch
[Triage Comment]
approved for beta - all three patches
Comment 11•4 years ago
|
||
bugherder uplift |
Comment 12•4 years ago
|
||
Comment on attachment 9204290 [details] [diff] [review]
bug1693883_utf8_provisioner.patch
[Triage Comment]
Approved for esr78
All three changesets
Comment 13•4 years ago
|
||
bugherder uplift |
Updated•4 years ago
|
Description
•