Skip to content

docs: clarify vanilla content nesting - #52

Closed
Frant1cc wants to merge 1 commit into
DavidHDev:mainfrom
Frant1cc:codex/docs-vanilla-content
Closed

Frant1cc wants to merge 1 commit into
DavidHDev:mainfrom
Frant1cc:codex/docs-vanilla-content

Conversation

@Frant1cc

@Frant1cc Frant1cc commented Nov 2, 2026 •

Copy link
Copy Markdown

What does this PR do?

Clarifies that content must reference a direct child of the source canvas when using vanilla HTML-in-Canvas components. Passing the outer container prevents HTML capture, even when the effect itself still renders.

Adds the note to both the installation guide and its copied Markdown.

Refs #49.

Type of change

  • Bug fix
  • New component
  • Component improvement
  • Docs / site
  • Other

Checklist

  • npx tsc --noEmit passes
  • npm run lint passes
  • npm run build passes
  • Tested in Chrome (with the html-in-canvas flag, if relevant)
  • Tested the WebGL overlay fallback (flag off / Safari / Firefox), if a component changed

Build verified locally with Node 22 using npm run build, including the prebuild generation steps. Browser testing was not performed. Component fallback testing is not applicable because no component code changed.

@Frant1cc Frant1cc closed this Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant