Issue #4357💬 AnsweredOpened May 31, 2022by adiux0 reactions

A border on the mj-column is shown twice in the editor

Quick answerby adiux

sorry, I just realized I posted this to the wrong repo. Created another issue at grapesjs-mjml.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome 102.0.5005.61

Reproducible demo link

https://codepen.io/adiux/pen/BaYrEXR?editors=1111

Describe the bug

How to reproduce the bug?

  1. Add grapesjs-mjml to the project with any version newer than 0.5.6
  2. Add a border to a section. E.g.: <mj-column border="4px solid #F45E43">
  3. Open MJML template with grapesjs

What is the expected behavior? only one border is shown: <img width="792" alt="image" src="https://user-images.githubusercontent.com/13075514/171250244-f96c395b-5a6e-4cde-a7f4-f60d778c9a15.png">

What is the current behavior? two borders are shown: <img width="766" alt="image" src="https://user-images.githubusercontent.com/13075514/171249926-6ed65f00-c09e-4c0c-a668-94fcc59fca0d.png">

If is necessary to execute some code in order to reproduce the bug, paste it here below:

// Working
import grapesjsMjml from "https://cdn.skypack.dev/[email protected]";

// Not working
import grapesjsMjml from "https://cdn.skypack.dev/[email protected]";
import grapesjsMjml from "https://cdn.skypack.dev/[email protected]";

Note: The rendered HTML is fine. It is only an issue with the editor.

Code of Conduct

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

Answers (2)

adiuxMay 31, 2022

sorry, I just realized I posted this to the wrong repo. Created another issue at grapesjs-mjml.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @adiux.

Great question about A border on the mj-column is shown twice in the editor. 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.