thunderbird / thunderbird/thunderbird-android

[ML 0.1/UI.03] - User Customization Integration

Open
#10,419 0 comments 0 reactions 2 assignees View on GitHub

@rafaeltonholo is already working on this.

Since Jan 23, 2026.

Dominant language
Kotlin
Stars
14k
Forks
2.8k
Avg merge
3d 3h
Merged PRs (30d)
57

Description

🎯 The objective

Connect the new Message Item UI to existing user preferences. This ensures the new design respects legacy customization options (density, colours, layouts).

[!NOTE]
This milestone might already be implemented once the others are done. Keeping this milestone for tracking regressions and feedback after the new UI lands to the user.

🎒 Resources

ℹ️ List all relevant resources like BugZilla meta bugs, Figma files, Notion links and other files. These can be filled in later.

🦮 Rules of the Road

🟢 In Scope
  • Enable MessageItem to change its spacing by user configuration
  • Enable MessageItem to change its number of preview lines by user configuration
  • Enable MessageItem background colour change only by user configuration
  • Enable Subject and Sender swap in MessageItem UI component
  • Hide Favourite button via user's settings
🔴 Out of Scope
  • Logic changes to the backend/database (visual only)
  • New preference creation (link to existing only)
🚧 Technical and/or Business Requirements
  • Spacing: Link the existing user preference for list spacing to the new UI component.
  • Preview Lines: Link the existing user preference for line count to the UI.
  • Background Colour: Ensure background color changes based on read status only if the user preference ("Change colour when read") is enabled.
  • Subject/Sender Swap: Link the existing preference to swap these fields in the layout.
  • Hide Favourite: Respect the preference to hide the star/favorite button.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.