TB 17 Content Plan

Open
#146 1 comment 0 reactions 1 assignee View on GitHub

@rtanglao is already working on this.

Since Jan 21, 2026.

Assessment

This issue has not been assessed yet.

Description

Android M: Knowledge: Android
Checklist of possible things to document
for a followup issue regarding the tall html email truncation problem:

Context:

When dealing with very tall messages, such as newsletters, the WebView cannot render them completely because they exceed the maximum size that the GPU can handle for a texture.

This was the primary reason the app was crashing. With recent changes to the WebView, we forced it to utilize the GPU layer for rendering. However, since it exceeded the maximum size on devices running API levels below 29, this would trigger a fatal crash.

Although the app no longer crashes, the WebView still cannot render the entire content, resulting in a truncated message. Users can still access all the messages, as long as they avoid using the "show all images" feature.

The goal of this issue is to investigate ways to resolve the truncation problem.

  • Email Account custom Avatars (if feature flag turned on), see Account Avatar Customization #10210 - revision 325042 with custom avatars
  • 2026-02-04 moved to TB17 from thunderbird/knowledgebase-issues#150, still under feature flag in 16 ; moved from thunderbird/knowledgebase-issues#151, TB 15, If beta testing is successful and feature flag is enabled on TB 15 release THEN --> Document that multiple indented threads (3 or 4 deep) result in single character lines of text. See comment below. Perhaps related to Bad column rendering in mails #9455 and also perhaps Wrap long lines when displaying message (text size gets too small) #3172 which was discovered in thunderbird/knowledgebase-issues#161 <-- fixed in TB15 beta under a feature flag . I believe still not in TB 15 release, move to 16
References
Dominant language
No language data
Stars
7
Forks
1
PR merge metrics
No merged PRs in 30d

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.

More from thunderbird/knowledgebase-issues

All issues in thunderbird/knowledgebase-issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.