The Beta version of the web client and the Android client do not correctly display the sender's name correctly in certain situations and will instead truncate the contents of the From: header.
To Reproduce
Steps to reproduce the behavior:
Receive an email that matches the characteristics in the examples below
The types of emails that cause an issue seem to be From: Someone via Mailing-List <mailing-list@example.org>
View the email
Expected behavior
The entire name of the sender should be displayed.
Screenshots
Here are some headers from an email with the issue:
From: YueCompl via Haskell-Cafe <haskell-cafe@haskell.org>
Reply-To: YueCompl <removed-for-privacy>
Content-Type: text/html
(CORRECT BEHAVIOR) Here's how the email renders in the old v3 web client:
(INCORRECT BEHAVIOR) Here's how the email renders in the new v4 web client:
(INCORRECT BEHAVIOR) Here's how the email renders on the Android inbox view:
Desktop (please complete the following information):
OS: Arch Linux
Browser: Brave
Version: Version 1.21.77 Chromium: 89.0.4389.90
Plugins: N/A
Resolution: N/A
URL: beta.protonmail.com
Smartphone (please complete the following information):
Device: OnePlus 3T
OS: Android
Additional context
As mentioned above, this isn't an issue in the old web client, so the behavior should just be changed to mirror that.
Describe the bug
The Beta version of the web client and the Android client do not correctly display the sender's name correctly in certain situations and will instead truncate the contents of the
From:
header.To Reproduce
Steps to reproduce the behavior:
From: Someone via Mailing-List <mailing-list@example.org>
Expected behavior
The entire name of the sender should be displayed.
Screenshots
Here are some headers from an email with the issue:
(CORRECT BEHAVIOR) Here's how the email renders in the old v3 web client:
(INCORRECT BEHAVIOR) Here's how the email renders in the new v4 web client:
(INCORRECT BEHAVIOR) Here's how the email renders on the Android inbox view:
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
As mentioned above, this isn't an issue in the old web client, so the behavior should just be changed to mirror that.