thunderbird / thunderbird/thunderbird-android

“Always show images”

Open
#8,700 7 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Checklist
  • I have used the search function to see if someone else has already submitted the same bug report.
  • I will describe the problem with as much detail as possible.
App

Thunderbird for Android

App version

8.2

Where did you get the app from?

Google Play

Android version

15

Device model

Google Pixel 8A

Steps to reproduce
  1. Go to “Account settings > Reading mail > Always show images”.
  2. Select “From anyone”.
  3. Check various emails for images.
Expected behavior

All images should be displayed exactly as they appear in the original email.

Actual behavior

Email containing in-line images are sometimes not displayed. Instead, there is usually (but not always) a button at the bottom of the email body which must be tapped to view them as attachments, causing confusion about where they originally appeared in context with the rest of the message.

Worse, in some other instances images are missing altogether, with a “broken image” icon displayed. In those cases, the bottom button is absent so there’s no way to view them at all.

All this behavior makes no sense to me considering the “Always show images” option is ticked.

Image

Logs

No response

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.

Research direction

Start by reproducing the problem in Thunderbird for Android 8.2 on Android 15: open Account settings > Reading mail > Always show images, select “From anyone,” and inspect emails with inline images. Compare images that appear inline, become attachments, or show as broken, then use the result to define what correct behavior should be.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.