I observed this one 115.3.0 this morning. Domain suffix wasn't cut off but the closing greater than symbol (>) got a bit cut off. This is on;y happening for me on newly arrived---and, it seems, unread--- message and a 1st reply to the new message. Subsequently reading it, replying to it, or even marking as unread and re-replying to it won't seem to trigger the issue.
Bug 1855276 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I observed this one 115.3.0 this morning. Domain suffix wasn't cut off but the closing greater than symbol (>) got a bit cut off. This is only happening for me on newly arrived---and, it seems, unread--- message and a 1st reply to the new message. Subsequently reading it, replying to it, or even marking as unread and re-replying to it won't seem to trigger the issue.
I observed this one 115.3.0 this morning. Domain suffix wasn't cut off but the closing greater than symbol (>) got a bit cut off. This is only happening for me on newly arrived---and, it seems, unread--- messages and a 1st reply to the new message. Subsequently reading it, replying to it, or even marking as unread and re-replying to it won't seem to trigger the issue.
I observed this one 115.3.0 this morning. Domain suffix wasn't cut off but the closing greater than symbol (>) got a bit cut off. This is only happening for me on newly arrived---and, it seems, unread--- messages and a 1st reply to the new message. Subsequently reading it / replying to it, or even marking as unread and re-replying to it won't seem to trigger the issue.