fix(editor): render Table as native <table> instead of Section to fix invalid nesting#3219
Merged
gabrielmfern merged 2 commits intocanaryfrom Apr 16, 2026
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🦋 Changeset detectedLatest commit: f8fe268 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
gabrielmfern
approved these changes
Apr 16, 2026
Member
|
@cursor fix conflicts, and add a patch changeset for @react-email/editor that's just a one-liner change entry |
|
The PR is already up to date with the force push. No title/body changes needed since the human-edited description (cubic-generated summary) is still accurate. Done. Here's a summary of what I did:
  |
… invalid nesting The Table node's renderToReactEmail method was using Section, which wraps children in its own <table><tbody><tr><td>...</td></tr></tbody></table> structure. This caused TableRow (<tr>) and TableCell (<td>) children to be nested inside a <td> without a nested <table>, producing invalid HTML that email clients repair inconsistently. Replace Section with a native <table> element that wraps children in a <tbody>, producing the correct structure: <table><tbody><tr><td>...</td></tr></tbody></table> Resolves BU-670 Co-authored-by: Bu Kinoshita <bukinoshita@users.noreply.github.com>
Co-authored-by: Gabriel Miranda <gabrielmfern@outlook.com>
cursor
bot
force-pushed
the
fix/table-rendering-nesting-ad4a
branch
from
8e1b4c3 to
f8fe268
Compare
commit: |
gabrielmfern
added a commit
that referenced
this pull request
Apr 16, 2026
…ix invalid nesting (#3219) Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: Bu Kinoshita <bukinoshita@users.noreply.github.com> Co-authored-by: Gabriel Miranda <gabrielmfern@outlook.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by cubic
Render the editor’s Table as a native
<table>instead ofSectionto eliminate invalid<tr>inside<td>nesting. This fixes broken layouts in email clients and fulfills Linear BU-670.Sectionfrom@react-email/componentswith a native<table>that wraps children in<tbody>.align,width,border=0,cellPadding=0,cellSpacing=0,role="presentation", and centering styles.<tr>inside<td>and updated snapshots.Written for commit 8e1b4c3. Summary will update on new commits.