Issue #4148πŸ’¬ AnsweredOpened February 18, 2022by varadero2 reactions

0.18.2 / 0.18.3 removes all on... HTML attributes when block is drag-dropped in the builder

Quick answerby Ju99ernaut❀ 1

That is the expected behaviour as stated in the release notes for 0.18.2

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome v99

Reproducible demo link

https://jsfiddle.net/jLo3qh7s/10/

Describe the bug

How to reproduce the bug?

  1. Create a block with content <input oninput="alert('123)" />
  2. Put that block into the builder
  3. Look at the HTML code

What is the expected behavior? All on... HTML attributes are retained

What is the current behavior? All the on... HTML attributes are removed

NOTE: Grapesjs 0.18.1 does not have this problem - 0.18.2 and 0.18.3 has it.

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

// your code here

Code of Conduct

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

Answers (3)

Ju99ernautβ€’ February 21, 2022

That is the expected behaviour as stated in the release notes for 0.18.2

artfβ€’ February 21, 2022

Correct. In case you need to enable unsafe attributes (at your own risk), you can do it via config.parser.optionsHtml.allowUnsafeAttr option.

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @varadero.

Great question about 0.18.2 / 0.18.3 removes all on... HTML attributes when block is drag-dropped in the builder. 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.