Description
Follow-up work for the Block Editor 2.0 effort tracked in #35262. This ticket groups several improvements and one backward-compatibility bug fix that surfaced during QA / dogfooding on dotcms.com. These items are intentionally scoped to land after the Block Editor 2.0 merger so we do not block that release.
Three areas of work are in scope:
-
Restore the attrs key on Block Editor nodes — backward-compatibility bug reported by Andres Paredes. In previous Block Editor versions every node had an attrs object (carrying level for headings, textAlign, href, etc.). In 2.0, attrs can be null, which crashes any client-side node-processing code that is not null-aware. This took down dotcms.com. A targeted fix was already shipped in the dotcms.com node-processing code, but we need to restore the key on the editor/output side so other customers do not hit this. Add tests that lock in the contract.
-
Native spell-check support — Will Ezell reported that right-click was being overwritten by the "Paste as Markdown" flyout, breaking the browser's native spell-check. "Paste / Copy as Markdown" has since been moved to the toolbar, so native spell-check should now work — we need to verify across supported browsers and add a regression check.
-
Rework table actions on the toolbar — Will Ezell flagged that table-related buttons (merge, add row, add column, etc.) consume too much real estate. Today they are auto-disabled when the user is not inside a table, but they still take up space. Several directions were discussed in Slack with Melissa from design. We need to align with design on the approach, then implement it while keeping all current table actions reachable.
-
[Object Object] bug when saving — Fatima reported that after making a few changes to a block editor content, and saving, all the content dissapeared and turned into '[Object object]'. This happened after modifying the editor content created and saved by another user.
Acceptance Criteria
1. Restore attrs key on nodes (highest priority — customer-impact bug)
2. Native spell-check support
3. Rework table actions on the toolbar
4. [Object Object] bug when saving
Priority
Medium (the attrs item is the highest-priority subtask because of confirmed customer impact).
Additional Context
Related: #35262 (Block Editor v2)
Slack discussion threads (#feat-block-editor-upgrade):
Description
Follow-up work for the Block Editor 2.0 effort tracked in #35262. This ticket groups several improvements and one backward-compatibility bug fix that surfaced during QA / dogfooding on dotcms.com. These items are intentionally scoped to land after the Block Editor 2.0 merger so we do not block that release.
Three areas of work are in scope:
Restore the
attrskey on Block Editor nodes — backward-compatibility bug reported by Andres Paredes. In previous Block Editor versions every node had anattrsobject (carryinglevelfor headings,textAlign,href, etc.). In 2.0,attrscan benull, which crashes any client-side node-processing code that is not null-aware. This took down dotcms.com. A targeted fix was already shipped in the dotcms.com node-processing code, but we need to restore the key on the editor/output side so other customers do not hit this. Add tests that lock in the contract.Native spell-check support — Will Ezell reported that right-click was being overwritten by the "Paste as Markdown" flyout, breaking the browser's native spell-check. "Paste / Copy as Markdown" has since been moved to the toolbar, so native spell-check should now work — we need to verify across supported browsers and add a regression check.
Rework table actions on the toolbar — Will Ezell flagged that table-related buttons (merge, add row, add column, etc.) consume too much real estate. Today they are auto-disabled when the user is not inside a table, but they still take up space. Several directions were discussed in Slack with Melissa from design. We need to align with design on the approach, then implement it while keeping all current table actions reachable.
[Object Object] bug when saving — Fatima reported that after making a few changes to a block editor content, and saving, all the content dissapeared and turned into '[Object object]'. This happened after modifying the editor content created and saved by another user.
Acceptance Criteria
1. Restore
attrskey on nodes (highest priority — customer-impact bug)attrskey on every node (nevernull).attrsis an empty object{}rather thannull.level,textAlign,href, etc.) continue to be emitted as before.2. Native spell-check support
3. Rework table actions on the toolbar
…menu pattern aligned with our design system.4. [Object Object] bug when saving
Priority
Medium (the
attrsitem is the highest-priority subtask because of confirmed customer impact).Additional Context
Related: #35262 (Block Editor v2)
Slack discussion threads (#feat-block-editor-upgrade):
attrsnull bug report (Andres Paredes): https://dotcms.slack.com/archives/C08MDK1BYLF/p1778615495898809