https://bugs.kde.org/show_bug.cgi?id=439680
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #10 from [email protected] --- Confirmed on KMail 6.7.1 (26.04.1), KDE Frameworks 6.26.0, Qt 6.11.1 on Manjaro Linux (Wayland). KMail HTML composer rewrites borderless tables to border="1" in outgoing HTML The issue is still reproducible. I tested multiple input methods: HTML signature editor, File, Command Inline editing of emailidentities config HTML pasted from Firefox RTF pasted from LibreOffice Drag & Drop HTML generated externally All of them produce the same result. The generated HTML is not semantically equivalent to the imported HTML. The HTML composer rewrites imported HTML signatures before sending. A simple borderless table <table border="0" cellpadding="0" cellspacing="0"> is serialized into the outgoing message as <table border="1" cellpadding="0" cellspacing="0"> causing visible black borders in all mail clients (Roundcube, Thunderbird, etc.). The borders are therefore part of the sent HTML and are not only a composer rendering issue. Steps to reproduce 1. Configure a HTML signature containing a 2-column table. Example: <table border="0" cellpadding="0" cellspacing="0"> <tr> <td><img src="..."></td> <td> <strong>Name</strong><br> Adress </td> </tr> </table> 2. Compose a message. 3. Send to another mail client (Roundcube, Thunderbird, Gmail). 4. Inspect the message source. Expected result: The outgoing HTML should preserve the table as <table border="0"> or otherwise serialize it without visible borders. Actual result: Outgoing HTML contains <table border="1"> which renders visible black borders around every cell. Modern HTML features (inline-block, spans, vertical alignment, etc.) are also simplified, altered or removed during serialization. This strongly suggests the content is imported into an internal rich-text model and later regenerated as HTML before sending. -- You are receiving this mail because: You are watching all bug changes.
