Backlog
Planned work for Thunderbird that is not currently on the roadmap.
Below is a listing of maintenance and feature work wanted for Thunderbird that is not currently on the roadmap. Interested contributors are welcome to grab any of the work below.
- 1.
- 2.
- 3.
- 4.
- 1.New address book UI: During the 91 cycle we already implemented the start of a new UI, in about:addressbook. The new address book lives in a tab. During the next cycle we will bring this implementation up to par with the old address book, and remove the old one. (Bug 1705276)
- 2.Improved storage: The current backend needs to be changed to support vCard data properly; e.g. arbitrary number of email addresses. Bug 469209
- 3.Non-standard data fields like “preferDisplayName” and “ChatName” should be dropped or moved out of the address book. Bug 1727298
- 4.Consider dropping the read-only OSX address book, and switch users over to using their read-write iCloud calendar through CardDAV.
- 5.“Meet with this person”/”Show conversations with this person” support (Bug 1638282, bug Bug 1731065)
- 6.
- 1.
- 2.UI work towards per-account SMTP - global SMTP (use the ISP SMTP for all accounts) is an abnormality nowadays. Bug 1731206
- 1.
- 2.
- 3.
- 4.Message body parsing in JavaScript: Libmime is the cruftiest piece of code we have: it is hard to understand and its maintenance is error prone. The library is used all over the place, so to the extent it’s possible we should start converting code over one part at a time. A number of years back the MIME header parsing was converted over to using the JSMime JavaScript library The message body is still using libmime for parsing. We should get started with using JavaScript for the body parsing of MIME. Add an option to use it so dogfooding can find problems. This is tracked in bug 1664150.
- 5.
- 6.Replace Mork for message index (bug 11050): create a global message index backed by a real database. Currently the index of messages is per folder (and based on Mork). This causes severe limitations to implementing a proper conversation view of messages. This work is tracked in bug 1572000.
- 7.
- 8.Compose back-end in JavaScript
- 9.
- 10.
- 1.
- 2.Fix how the calendar widgets interact with the backend: this will facilitate code sharing. bug 1727711, bug 1753558, bug 1763752, bug 1763753
- 3.
- 4.ical.js: Putting effort into making ical.js performant enough will let us drop our very old fork of the C++ libical and focus on making the JavaScript implementation great. Tracked in bug 978570.
- 5.
- 6.
- 7.
- 8.Integrate something like the birthday calendar provider, linking contact birthdays to the calendar view. (Bug 151994)
- 9.Holiday calendar auto-setup. Allow users easy subscription to holiday calendar for their region. Bug 1731117
- 10.iMIP event invitations improvements
- 1.what changed is confusing
- 2.make it more human, not so techy and formal
- 3.allow setting RSVP status manually (of others),
- 4.For the organizer, the data should become accessible (e.g how many people *are* coming to my event in the end)
- 5.add UI reminders when not responded
- 6.See timezone for attendees when trying to schedule meetings. Timezone to be added to the contact information.
- 7.check status on server *before* updating
- 11.
- 12.
- 13.Improve usability when interacting and viewing events: easier to see and interact with the data, e.g. tojoin a video call link. Bug 1685007
14. Improve the keyboard accessibility of the entire Calendar tab: bug 1717692
15. Implement a date picker when calendar sidebar is collapsed (no mini month quick access):
bug 1717692
- 1.Investigate inlining styles of replies so that styling is contained within the quoted text. Bug 1731198
- 2.
- 3.
- 4.
- 5.
- 6.
- 7.
- 8.Editor dialog removal - we have too many “web page element editing” type dialogs which make very little sense when editing mails. Bug 1731213
- 9.
- 10.
- 1.
- 2.Matrix provisioning - allow people to sign up for hosted Matrix from within Thunderbird.
- 3.UI renewal
- 4.
- 1.
- 2.Make filelinks work more like normal attachments: adjust the inserted “ad”, and have the fake file be something useful. Bug 1670791
- 1.
- 2.
- 1.
- 1.Replace the 3pane implementation. Instead of one global data view we should have one view per tab (bug 1729379). - Deferred to 114
- 2.
- 1.folder pane
- 2.thread pane
- 3.
- 1.
- 2.Replace elements and attributes that can’t be web compatible. Aim to have documents that would gracefully degrade if viewed without XUL.
- 3.Continue replacing elements that have good HTML replacements (exactly which to take on first needs investigation)
- 4.Threaded (conversational) view of messages
- 5.Consider changing default thread/message order - newest on top? Threaded view by default.
- 6.
- 7.Firefox Monitor integration - let people know if their account was exposed in a data breach. Bug 1731228
- 8.Mail meta-data exposure (micro-data, JSON-LD)
- 9.
- 10.IMAP notes? Storing text notes on the IMAP server would be useful, and the feature is low hanging fruit not necessarily very hard to implement. Tracked in bug 713843.
- 11.Printing CSS (mostly) improvements: make the printed mails/calendars/address books look nice.
- 12.Spaces toolbar: Implement an easier and more convenient way to move between the different parts of the application (mail, calendar, tasks etc.) Tracked in bug 1665511.
- 13.Rebuild the message header. The message header has a bit of messy source code, and with the removal of the customizable toolbar, it seems necessary to do a good clean up and rethink the UI to better highlight sections and make the whole area properly responsive. Mock-up:
- 14.Mail data utilization and integration
- 1.detect structured data (JSON-LD), allow acting on that data (see schema.org, xref KItinerary) — e.g. let you add flight data into your calendar directly
- 2.detect micro-formats [related to smart-widgets]
- 3.detect the most common free texts (especially: times and dates), and allow inline viewing of calendar schedules for that time, or contact information for a known contact in your address book etc.
- 4.improved support for drag-n-drop as well as copy-paste of many data types: mail data, events, contacts
- 15.Implement a new icon theme with symbolic and hicolor variation, and predefined color schemes for the folder pane icons users can select.
- 16.Make more areas of the UI be sensitive to the Density pref.
- 17.Implement a UI pref to change the font size of the entire app.
- 18.Implement a more solid design system with consistent colors, spacings, font-sizings, etc., in order to be more independent from the variable changes coming from m-c and reduce the amount of visual regressions and upstream syncs.
- 19.Support mailing list management headers (List-Unsubscribe, List-Archive, List-Post, List-Archive). Bug 29041.
- 1.
- 2.
- 3.
- 4.
- 5.
For localization Firefox is moving (https://arewefluentyet.com/) to Fluent, and Thunderbird should follow.
Firefox has officially deprecated the old style localization system since October 2019. Thunderbird should do the same: i.e. adding/changing strings only allowed for Fluent strings, with properties/dtd files basically freezed.
- 1.Fluent-migrations for the main windows
- 1.Add iframes to the Thunderbird UI where WebExtensions need to load custom content, similar to the sidebar of Firefox. This could be added as a dedicated API or per use-case to the individual APIs (calendar, addressBook, mailTabs), see bug 1693543.
- 2.Add a DNS API for advanced DNS requests (not just A records).
- 3.Add a Sessions API to allow WebExtensions to store/access session data (similar to what is provided by Firefox).
- 4.Work on internal message handling, so WebExtension can identify messages across sessions with the same id.
- 5.Allow for additional customization and add an overflow container for action buttons, if UI space is exhausted.
- 6.Support better theming/UI integration of WebExtension option tabs
- 7.
- 8.Rework the contacts APIs to fix existing gaps like missing photo access, align with the new address book and permit add-ons to provide their own address books.
- 9.Figure out a way forwards for file system access (Chrome FileSystem API?) together with Mozilla core.
- 1.Encrypt if possible (guided TOFU): Like SSH, we should move more towards trust on first use (TOFU). This would be more feasible if all incoming keys were automatically collected for possible usage later (Bug 1667564) - at the moment without chores for the user, it does not work since the keys are not “known”, even if they have been sent to you. Bug 135636/ bug 1627956.
- 2.Publish to keyserver: We should allow users to publish their key on the openpgp keyserver for others to discover. Bug 1731232
- 3.
- 4.More automated tests
- 5.Code cleanup: The code needs cleanup, e.g. to remove old code that we don’t use or that is no-op for other reasons.
- 6.
- 7.UX improvements to make it easier to use encryption: No internal knowledge of how OpenPGP works should be required to use encryption (setup should educate what’s needed).
- 1.
- 2.
- 3.Phabricator - let’s try to get everybody using this...
Last modified 8mo ago