4 ms·
The biggest problem I have with thunderbird is that it fails to render some html mails properly. Above all, they should fix this problem first. Instead of creat
by stewbrew 9y ago
The biggest problem I have with thunderbird is that it fails to render some html mails properly. Above all, they should fix this problem first. Instead of creating a mobile app or whatever, they should get their existing client right. As of today, the 2 things that keep me from switching fully to evolution are (1) evolution's unfriendly keyboard shortcuts that, for whatever reason, I cannot change, and (2) nostalgy.
- bzbarsky 9y agoHave you filed bugs about this, with the example emails attached? Thunderbird uses the same exact HTML/CSS renderer as Firefox. To the extent that it's not rendering mails "properly", those mails are clearly expecting to be rendered in a way different from what the HTML/CSS standards say... It's possible to make this work, if needed, but the developers would need to at least know what standard-deviating behaviors are needed.
- gsich 9y agoHTML mails are an abomination, just tell people to use text/plain.
- fs111 9y agohahahaha, you are funny
- u801e 9y agoCould Thunderbird be configured to open a web browser to display the message if it's not rendered properly?
- jcranmer 9y agoThunderbird uses Gecko, the same engine as Firefox, to render emails. This means it's actually generally the most-compliant HTML rendering email of any email client: you can even use MathML and <video> if you want to (assuming that the bug about <video> controls requiring JS has been fixed). The three caveats to this statement that might apply: 1. Thunderbird loads the message in quirks mode. 2. cid: links in CSS aren't going to load properly (and other resource URLs are generally blocked by default). 3. Different HTML sections in a message can leak together, largely due to there lacking a good way to combine multiple HTML documents into a single scroll frame (if any Gecko layout folks are reading this, can you please fix https://bugzilla.mozilla.org/show_bug.cgi?id=80713 https://bugzilla.mozilla.org/show_bug.cgi?id=80713 ?).