- separate the folder colors into their own file to be imported where needed
- convert colors.css to use hex instead of rgb as to be more easily used in javascript
Differential Revision: https://phabricator.services.mozilla.com/D155263
--HG--
extra : moz-landing-system : lando
We're spinning the event loop in markMessages() waiting for _uidlMap to be set. But inside _loadUidlState there is internal waiting after _uidlMap is set.
Set _uidlMap late enough that there won't be any internal async functionality after it.
Differential Revision: https://phabricator.services.mozilla.com/D160007
--HG--
extra : amend_source : 9e1a1fda4164fbe49968c5a0066d80804afbf8b9
- Refactor icon to use label element instead of xul:image
- Replace icon in new list dialog and edit list dialog
Differential Revision: https://phabricator.services.mozilla.com/D159379
--HG--
extra : moz-landing-system : lando
These prefs are not used anymore by Thunderbird (they are for Seamonkey, so they
are #ifdef wrapped in mailnews.js). The javascript is not loaded by Thunderbird,
but is still shipped.
Removing these prefs allows for cleanup of l10n.toml and should mean that the
remaining prefs will be exposed for localization in Pontoon again.
Differential Revision: https://phabricator.services.mozilla.com/D158869
--HG--
extra : moz-landing-system : lando
The common file name length limit is 255. On windows 255 chars, on linux 255 *bytes*.
In UTF-8 one char can take up up to 4 bytes, but 3 covers all normal cases.
Use a limit of 255/3 = 85 chars for file names to be safe. That will also make for more reasonable file names in general usage.
Filenames longer than 85 will turned into first 74 char ... 10 last chars.
Differential Revision: https://phabricator.services.mozilla.com/D158825
--HG--
extra : rebase_source : fd89bc49487ff42f01bdf6e6fda759439f5fa8b5
extra : amend_source : ac63839a807a7841b9e48a5c27f19cb933bacbfb
Non-ascii characters in ldap filter are percent encoded when saving, need to decode when constructing nsILDAPURL back.
Differential Revision: https://phabricator.services.mozilla.com/D159004
--HG--
extra : rebase_source : 8a353937f62b2251bd4a08cc34be95d755e86ed5
Update nsIDBFolderInfo.knownArtsSet based on XOVER range, doesn't matter if artciles in the range don't exist on the server.
Differential Revision: https://phabricator.services.mozilla.com/D158898
Also took the opportunity to constify the buffer passed in to
DeliverQueuedLine(), in anticipation of one sweeping away all
the malloc-based buffer complications.
Differential Revision: https://phabricator.services.mozilla.com/D158818
--HG--
extra : amend_source : 0f7d67c84ebeae920fd51927c59747f3789c67dd
extra : absorb_source : f521915c9cdda71eb7a7d9bf66c0272540168072
Introduce MsgProtocolInfo.sys.mjs to reuse code between nntp/pop3/imap protocol info modules.
Differential Revision: https://phabricator.services.mozilla.com/D158739
--HG--
extra : moz-landing-system : lando
When possible, we redirect to the AB tab and let that code handle the dialogs.
Otherwise we open a subdialog from where we are.
Differential Revision: https://phabricator.services.mozilla.com/D158357
--HG--
extra : moz-landing-system : lando
The problem was that NntpClient was handling escaping the "." message
termination, but that nsNewsFolder::NotifyDownloadedLine() was scanning for
"." lines to finish messages. So the folder would screw up when a message
body contained a lone "." line.
The changes in detail:
- Adds notifyDownloadBegin()/notifyDownloadEnd() calls to nsIMsgNewsFolder.
- In NntpClient.jsm:
- Now calls notifyDownloadBegin()/notifyDownloadEnd() to denote message
boundaries.
- No longer sends a "." final line to the folder.
- Tries to call notifyDownloadEnd() with an error code if an error occurs.
- adds an status param to nsMsgDBFolder::EndNewOfflineMessage(), and a code
path to clean up upon errors. News folder now uses this to handle rolling
back if an error occurs, but IMAP still relies on magic (checking the size
of the message written so far).
- nsNewsFolder::NotifyDownloadedLine() no longer looks for a lone "." to
denote the end of a message. The relevant code was split out into
NotifyDownloadBegin() and NotifyDownloadEnd().
- Added some comments to try and clarify the offline message writing vars in
nsMsgDBFolder.
Differential Revision: https://phabricator.services.mozilla.com/D158486
--HG--
extra : absorb_source : 14534b426ccbe4239cb916c35c057ed46f3f6a4e
Call parseAdoptedMsgLine only when downloading for offline.
Differential Revision: https://phabricator.services.mozilla.com/D158015
--HG--
extra : histedit_source : 35326dad81be0a671851946449b9af9ab7267b5d