Issue #5549πŸ’¬ AnsweredOpened December 6, 2023by driskell0 reactions

Mj-preview is not editable

Quick answerby artf

This is not core related issue and probably not an issue at all as <mj-preview> is not supported by default in mjml plugin

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Safari 17

Reproducible demo link

https://grapesjs.com/demo-mjml.html

Describe the bug

How to reproduce the bug?

  1. https://grapesjs.com/demo-mjml.html
  2. Go to view code - copy the MJML
  3. Go to import code - paste in the MJML and add to the top <mj-head><mj-preview>Some preview text</mj-preview></mj-head>
  4. Now try to edit it
<img width="878" alt="Screenshot 2023-12-06 at 14 23 53" src="https://github.com/GrapesJS/grapesjs/assets/939815/2d6ab784-c6b5-4de4-a522-d6f4ed076eee">

What is the expected behavior?

Should be able to edit - or it shouldn't be visible in the editor.

What is the current behavior? It displays top left, with default font, no padding, and is not editable. In previous versions of grapeJS builder it is in fact editable, but if you edit it too short the highlight "BODY" gets in the way and you can never get back to editing it. Further, if you empty it, it seems unreachable in the editor completely but the gap is still there.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (4)

artfβ€’ December 7, 2023

This is not core related issue and probably not an issue at all as <mj-preview> is not supported by default in mjml plugin

driskellβ€’ December 8, 2023

@artf Sorry I don't understand. It’s an issue as detailed. Is it something to raise on the other repository? I’m not familiar with the internals here so don’t know what it is that the GrapesJS/mjml needs to support in order for this repository to not display it

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @driskell.

Great question about mj-preview is not editable. The recommended approach with GrapesJS is to use the event-driven API.

Start here:

  1. Check the GrapesJS documentation for your specific module
  2. Look for the on() event listener method
  3. Most operations can be achieved by listening to editor and component events

Common patterns:

// Listen for changes
editor.on('change', () => console.log('something changed'));

// Component lifecycle
editor.on('component:mount', (c) => console.log('component ready', c));
editor.on('component:update', (c) => console.log('component updated', c));

If you're still stuck:

  • Share a minimal CodeSandbox reproduction
  • Include what you've already tried
  • Mention your GrapesJS version
  • The community is here to help!

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins β†’
Premium option

Premium plugins ship with support, regular updates, and production-ready features β€” save days of integration work.

Browse premium plugins β†’

Related tutorials

In-depth guides on the same topic.

All tutorials β†’

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.