Tell us what should happen
Tell us what happens instead
I see a floating bar with undo/redo buttons.
When I check the 3 dots drop-down, the checkbox Enable formatting is disabled.
As a side note, I didn't find any setting to define a default behavior for this, although mentioned in https://github.com/nextcloud/mail/pull/1988#issuecomment-539848160
Mail app version: 1.3.4
Mailserver or service: gandi.net
Operating system: Raspbian 10
Web server: nginx
Database: MariaDB
PHP version: 7.3
Nextcloud Version: 18.0.4
Browser: (e.g. Firefox 48) Opera 68, chromium-based, Firefox 76
Operating system: (e.g. Arch Linux) Linux Mint 19.3
Do you have a screenshot for us? Are there any js errors on the console?
The problem its the writing mode and it only happens on the 18th version. The rich text doesn't save. If you click Rich Text and you go and reply an email or write a new email, and go back to writing mode, the one clicked its the plain text. @mat-m can you confirm?
I have the same problem. Either answer an email or write a new one, the WYSIWYG editor does not show up when enabling the "Enable Formatting" checkbox in the "..." context menu bottom right.
The checkbox automatically unticks immediately after closing the context menu.

When typing:
[DEBUG] mail: TextEditor input changed to <<p style="margin:0;">asdasdads</p>>
Object { app: "mail", uid: "xyz" }
Nextcloud (Docker container version), 18.0.4 behind Nginx proxy
Browser: Firefox 76, Chrome 83
I can confirm the bug.
Whatever is set as default (plain or rich text) for an account, the switcher check box in the composer doesn't react to a change to the respective other.
Tested with 1.3.5 and 1.4.0 Beta 2
Yep, @GretaD is working on it :)
My insights from yesterday are that https://github.com/nextcloud/mail/pull/2874 broke it.
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.
@ChristophWurst vs no-response bot
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.
What is going on
Somebody/something wants to keep you away from the weekend - or force you to?
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.
This is might be explanation: "closes issues where the author hasn't responded to a request for more information"
I deleted the "needs info" label. Maybe it helps???
Oooooof. Of course it was because of that label :see_no_evil: