To provide a real-time update experience, how should a custom block update the canvas when a user makes changes?

• A. Update only when the user saves.
• B. Do not update the canvas.
• C. Update in real time using setContent or setSuperContent on changes.
• D. Use setData only to update visuals.

Answer: (C)

Updating the canvas in real time as the user changes settings creates an immediate, live preview of what the block will look like. The best approach is to hook into user changes and re-render by using setContent or setSuperContent with the new values. This keeps the canvas in sync with the current input, giving a responsive, WYSIWYG-like experience.

If you wait until save, the user sees nothing reflect their edits while they’re changing them, which breaks the intuitive feedback loop. Not updating the canvas at all defeats the purpose of a preview, and using setData alone won’t drive the visuals—the rendering should come from updating the content itself.

In practice, update the relevant content state as changes occur: use setContent to refresh the block’s inner content and setSuperContent for higher-level or surrounding content, ensuring the visual canvas mirrors the latest user input.