Summary

Fix canvas rendering of CMS-bound rich text fields where all block elements (headings, paragraphs, lists) were incorrectly rendered as <span> instead of their proper HTML tags. Also fix the layers tree not showing the collapse arrow for CMS-bound rich text layers.

Closes #69

Changes

• Propagate useSpanForParagraphs flag through renderInlineContent and renderNestedRichTextContent instead of hardcoding true
• Rich text layers (<div>) now render CMS content with proper block tags (<h1>, <p>, etc.)
• Restrictive tags (<p>, headings) still use <span> to avoid invalid HTML nesting
• Add hasRichTextContent() helper that detects CMS field bindings for collapsibility without requiring resolved data
• Use hasRichTextContent() in LayersTree for collapse arrow visibility

Test plan

• Create a CMS page with a rich text layer bound to a rich-text field
• Verify headings render as <h1>-<h6>, paragraphs as <p>, lists as <ul>/<ol> on the canvas
• Verify no <p> cannot be a descendant of <p> console errors
• Verify the rich text layer shows the collapse arrow in the layers tree when bound to a CMS field
• Verify expanding the layer shows the correct sublayers from the CMS content
• Verify non-CMS rich text layers still work correctly (proper tags, collapsible)
• Verify a <p> text layer bound to a rich-text CMS field still uses <span> (no nesting errors)

Made with Cursor