Issue #3549πŸ’¬ AnsweredOpened June 19, 2021by anlumo0 reactions

CreateCustomEvent Doesn't Handle Mouse Events Correctly

Quick answerby ClaudeCode

Thanks for reporting this, @anlumo. The issue with createCustomEvent Doesn't Handle Mouse Events Correctly appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state. What to try: Add a setTimeo...

Read full answer below ↓

Question

Version: 0.17.4 / git master

Describe the bug detailed

FrameView repackages keyboard and mouse events here:

https://github.com/artf/grapesjs/blob/07061ae1307fedf2a3b9bd585ce0cb30f653f112/src/canvas/view/FrameView.js#L389-L399

I think the reason is related to redirecting iframe events to parent frame events. This would be fine, however, the createCustomEvent function looks like this:

https://github.com/artf/grapesjs/blob/07061ae1307fedf2a3b9bd585ce0cb30f653f112/src/utils/dom.js#L63-L81

As you can see, the which property is defined to return the value of keyCode. This works for keyboard events, but on mouse events, it should return the value of which from the wrapped event.

This causes which to be undefined in the event, breaking an external package I use that relies on event.which for mouse events.

Answers (1)

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @anlumo.

The issue with createCustomEvent Doesn't Handle Mouse Events Correctly appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.

What to try:

  1. Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
  // your operation here
}, 0);
  1. Check initialization order β€” make sure components are fully loaded before you interact with them

  2. Use the editor's event system β€” listen to completion events:

editor.on('component:mount', (component) => {
  // safe to interact with component here
});

Recommended next steps:

  • Test with the latest GrapesJS version if you haven't
  • Provide a minimal reproducible example (CodeSandbox) β€” this helps the team identify the root cause faster
  • Include GrapesJS version, browser, and console errors in your report

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.