Client compatibility and proofs
What is automatically proven, and the manual email-client QA checklist that closes the remaining gap.
Nuxt Email separates automated compatibility evidence from manual client results.
What is automatically proven
The conformance suite compares covered behavior with fixed React Email versions. It checks exact bytes, normalized output, or specific semantics. Presentation tables, Outlook-specific button spacers, preview hiding, font declarations, and Tailwind inlining have regression cases.
This is useful implementation evidence, but it is a comparison to a reference renderer, not proof that every email client will display a message identically.
Completed beta smoke test
Matthias completed the owner-run 1.0.0-beta.1 smoke test on 2026-08-22. The same proof-kit message passed in Gmail web, Apple Mail on macOS, and Outlook classic on Windows in light and dark modes. The signed QA record records the tested commit and artifact hashes.
This smoke test is enough for the published beta. It does not complete the full eight-client checklist required for stable 1.0.0. An external transactional beta also remains pending.
Run the stable checklist
Automated tests do not open real email clients. Run the stable checklist against the fixed proof-kit fixture.
Render the fixture
Run pnpm proofs:generate, then use the committed proof-kit template and props. Optionally replace only the logo URL with an HTTPS image you control.
Send with your own account
Send the exact rendered html and text to test mailboxes through a provider SDK you choose. Nuxt Email does not send mail.
Inspect in three clients
Open the same message in Gmail web, Apple Mail (macOS or iOS), and Outlook for Windows.
Record the result
Note client versions, screenshots, defects, and a final accept/reject decision.
Required checks
- Inbox preview shows only the intended preview sentence and does not expose filler characters.
- The remote logo has useful alternative text when images are blocked.
- Heading, paragraphs, divider, and footer links retain readable spacing.
- The activation button is clickable, visually centered, and has comparable horizontal and vertical padding in Outlook.
- Two columns stay in one row at desktop email widths and remain readable when the client narrows the message.
- Link destinations and the
mailto:link are correct. - Plain-text fallback contains the meaningful content and destinations but excludes preview filler and images.
- No script, hydration payload, framework state, or event-handler attribute is present.
1.0.0 still waits for the full eight-client record and external beta evidence.