Issue #4168πŸ’¬ AnsweredOpened February 28, 2022by m-jojo-s0 reactions

Hover not toggled until next mouse-enter

Quick answerby ClaudeCode

Thanks for reporting this, @m-jojo-s. Great question about hover not toggled until next mouse-enter. The recommended approach with Components is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific module Look for the on() event listener method Most operations can be achieved by...

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome Version 98.0.4758.80 (Official Build) (arm64)

Reproducible demo link

https://jsfiddle.net/01pa5mty/9/

Describe the bug

also thank you for adding hover:before and select:before events, will be really useful!

How to reproduce the bug? (Steps for reproducible demo)

  1. Add any container block
  2. Add a text block and select anything besides text and immediate parent. (selection, highlight, hover for text gets disabled as expected).
  3. By keeping cursor on top of the text, select the parent cell. Cell gets selected and selection,highlight,hover for text is enabled but gjs-hovered class isn't added until mouse exits and re-enters the text component.

What is the expected behavior? Component shows as hovered and highlighted on enabling both properties while cursor is on top of the component.

What is the current behavior? Cursor needs to re-enter the component to trigger highlight and hover

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

editor.on('component:mount', component => {
    if (component.is('text')) {
      component.set('highlightable', false);
      component.set('selectable', false);
      component.set('hoverable', false);
    }
});

editor.on('component:selected', component => {
		component.components().map(child => {
    		child.set('highlightable', true);
	      child.set('hoverable', true);
	      child.set('selectable', true);
    });
});

Code of Conduct

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

Answers (1)

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @m-jojo-s.

Great question about hover not toggled until next mouse-enter. The recommended approach with Components 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.