[GH-ISSUE #1000] Being mistakenly warned about an empty email body #537

New issue

Closed

opened 2026-02-25 21:35:17 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 21:35:17 +03:00

Owner

Originally created by @PaulTGG on GitHub (May 3, 2024).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/1000

Originally assigned to: @mercihabam on GitHub.

🐛 Bugreport

#866 was done to allow sending emails where there is no text in the body. Since then, the compose page has been updated, and now, it's possible to get the message warning of an empty email body when there actually is text in the body. Not sure if this also has something to do with the visual glitch where the word "message" appears over the toolbar (also seen in the screenshot below).

Version & Environment

Rev: 492f634

Steps to reproduce

Compose an email
Type in the recipient and subject
Add text to the body
Click Send. The message pops up.

Originally created by @PaulTGG on GitHub (May 3, 2024). Original GitHub issue: https://github.com/cypht-org/cypht/issues/1000 Originally assigned to: @mercihabam on GitHub. ## 🐛 Bugreport #866 was done to allow sending emails where there is no text in the body. Since then, the compose page has been updated, and now, it's possible to get the message warning of an empty email body when there actually is text in the body. Not sure if this also has something to do with the visual glitch where the word "message" appears over the toolbar (also seen in the screenshot below). ![send error](https://github.com/cypht-org/cypht/assets/12187131/6aba381a-5270-48dc-bc52-b880da80412e) ### Version & Environment  Rev: 492f634 ### Steps to reproduce 1. Compose an email 2. Type in the recipient and subject 3. Add text to the body 4. Click Send. The message pops up.

kerem closed this issue

2026-02-25 21:35:18 +03:00

kerem commented

2026-02-25 21:35:18 +03:00

Author

Owner

@mercihabam commented on GitHub (May 7, 2024):

PR https://github.com/cypht-org/cypht/pull/1006

@mercihabam commented on GitHub (May 7, 2024): PR https://github.com/cypht-org/cypht/pull/1006

kerem commented

2026-02-25 21:35:18 +03:00

Author

Owner

@PaulTGG commented on GitHub (May 7, 2024):

I still have the same issue with the latest master as of this moment (117f04b).

@PaulTGG commented on GitHub (May 7, 2024): I still have the same issue with the latest master as of this moment (117f04b). ![bodynotempty](https://github.com/cypht-org/cypht/assets/12187131/9bf23189-8dfd-4fb5-beab-68030f07d4e9)

kerem commented

2026-02-25 21:35:18 +03:00

Author

Owner

@mercihabam commented on GitHub (May 7, 2024):

@PaulTGG Sure, the PR is still open. On master, you should still be getting the same behavior.
Maybe try it directly from the pull request?

@mercihabam commented on GitHub (May 7, 2024): @PaulTGG Sure, the PR is still open. On master, you should still be getting the same behavior. Maybe try it directly from the pull request?

kerem commented

2026-02-25 21:35:18 +03:00

Author

Owner

@PaulTGG commented on GitHub (May 8, 2024):

@jacob-js Sorry about that - I wasn't paying close attention. I tried from the PR, and it works now, thanks!

@PaulTGG commented on GitHub (May 8, 2024): @jacob-js Sorry about that - I wasn't paying close attention. I tried from the PR, and it works now, thanks!