Loading today’s stories
Build1 distinct publisher3 min readPublished Updated
A dev.to team traced four reproducible signature failures to Word's layout engine, a dark-mode color pass, a macOS Mail checkbox and a length limit. Only the checkbox is out of reach of anything you can emit.
The Engineer · Build desk
Compiled by The EngineerSomething wrong?How this is made
Word has no max-width in its vocabulary [6]. That is the whole of the Outlook bug. The engine will use `width="80"` if the markup gives it one [10]; absent that, the only size information left in the document is the file's own dimensions, so a 600x600 retina asset renders at 600 [7]. Against an intended 80, that is 7.5x on each edge and roughly 56 times the area [9]. The writeup's own bullet list quotes a 2000px banner instead [8], and the disagreement is the useful part: the blowup scales with whatever asset you shipped, so there is no fixed pixel count to assert in a test. What you assert is that every `img` carries width and height attributes.
The inversion bug has a different shape. Gmail and Apple Mail run a color transform over background and border properties once the OS reports a dark theme [12]. White is pushed toward #1e1e1e or #333333, while light and transparent container borders go the other way, into high-contrast lines [14]. So the fix is subtractive. Force `border: none` on the parent table and on every descendant `td`, alongside `cellpadding="0"`, `cellspacing="0"`, `border="0"` and the `mso-table-lspace`/`rspace` resets [15], and the inversion pass has no border primitive left to act on [16].
The typography failure is not in the file at all. macOS Mail's Signatures pane carries a checkbox, "Always match my default message font", ticked by default on many versions of macOS, and while it is ticked Mail strips inline `font-family`, `font-size` and font color as it composes [18]. Nothing you emit reaches that setting. A generator can ship a font stack and an instruction; it cannot ship the tick.
Two of these fixes pull against each other. Dark-mode hardening is per-node by construction, and those bytes land in the same Gmail signature field that rejects oversized input [19]. The piece demonstrates that limit without quantifying it, which means the number worth measuring before you adopt the pattern is your own emitted size.
The 64% figure [3] was measured where people go to complain: 2,529 comments under 25 tutorials with 18.6 million views between them [2], which works out to more than 1,618 requests for a fix [4]. Viewers whose signature worked had no reason to type anything. For that ratio to describe your recipients you would need the count of quiet successes, and nobody has it. The renderer facts transfer regardless, because the Word engine behind classic Outlook on Windows does the same thing to everyone's markup [5]. The length ceiling does not transfer; it belongs to Gmail's signature field, not to the body of a campaign send. (The piece also opens with 4.5 billion people sending email every business day [20], which is the one number in it I would not carry into a spec.)
Ranked by verification strength, evidence, and original report placement.
In Apple Mail, custom brand typography is stripped away and replaced with standard 12pt Helvetica.
macOS Mail Settings > Signatures contains a checkbox titled "Always match my default message font", which is ticked by default on many macOS versions, and when ticked Apple Mail strips all inline font-family, font-size and font-color declarations when composing messages.
Copying a layout from Google Docs or Sheets injects 15,000 characters of hidden XML bloat, causing Gmail to error out with "The signature is too long".
A dev.to writeup, "Why Email HTML in 2026 is Still a Nightmare: Reverse-Engineering Dark Mode & Outlook MSO Tables", describes building a zero-bloat HTML email signature compiler.
Classic Microsoft Outlook on Windows (Outlook 2016, 2019, 2021 and Office 365 desktop) still uses Microsoft Word (MSO) as its HTML layout engine.
Word's rendering engine does not support CSS flexbox, CSS grid, max-width, min-width, object-fit, or border-radius on images.
Distinct publishers with included, body-backed reporting in this cluster.
dev.to
1 article · August 29, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
build
Let the agent propose, not commit: the envelope that has to arrive before a write1 distinct publisher
build
Three manual interventions in a month, and every guard was working as designed1 distinct publisher
build
Six MariaDB versions, one real difference: the only reason to leave 10.6 is the July 2026 clock1 distinct publisher
build
Force the tool call, then hand Lightsail a long-lived key1 distinct publisher
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Testable mechanics, decorative numbers
The load of this story sits on claims that die instantly if wrong: Word ignoring max-width, Google Docs emitting border: 1px solid #ffffff where the user asked for nothing, a named checkbox in a named settings pane. Anyone with a Windows Outlook and a Docs table can check them this afternoon. Everything with a digit in it is the opposite — the 2,529-comment scrape has no dataset, list or date, the 15,000-character bloat figure is a round assertion, and the post's own 600px example refutes the 2000px banner in its opening bullets.
A generator with nobody on the record using it
What has demonstrably shipped is a free generator, announced by the people who wrote it, and nothing more: no repository, license, install count, named deployment or third-party integration appears anywhere in this reporting. The 18.6 million views the authors lean on are other people's YouTube traffic on other people's tutorials — evidence that the problem attracts an audience, not that this solution has one.
Vocabulary running ahead of the findings
'Nightmare', 'bulletproof', a headshot 'monstrously' inflating to 2000px — the register is far hotter than the substance, which resolves to cellpadding resets, paired width/height attributes and an unticked preference box, all of them decade-old trade knowledge among email developers. The gap is smaller than the adjectives suggest because the underlying mechanics do hold up; it is real because the loudest number in the piece is the one its own code contradicts, and because a 4.5-billion-senders opener is doing rhetorical work no citation supports.
The problem sizing and the product share an author
This is a launch wearing a teardown's clothes. The same team defined the four failures that matter, quantified how much users suffer from them, and then presented the free compiler engineered to absorb precisely those four. None of that makes Word's layout engine less broken — but the selection of which failures count, and the 64% figure establishing that they count, come from the party with something to ship.
One account, almost internally consistent
With a single author and no corroborating report, our read rests on whether the post agrees with itself — and it largely does, until the opening bullets and the image example part company over how big a broken headshot becomes. We sit mid-range deliberately: the checkable parts are checkable by any reader, which is not the same as anyone having checked them, and the hedge about which macOS versions ship that checkbox ticked is left unresolved.