The blue outline (gjs-hovered) is not following its parent during scrolling
Would be nice to have this fixed, not the end of the world, but mildly annoying.
Read full answer below ↓Question
Version: 16.27
Are you able to reproduce the bug from the demo?
[x ] Yes [ ] No
Describe the bug:
I discovered an issue with gjs-hovered, the class that handles the mouse-hover outline for elements. Sometimes the blue outline will move relative to its parent during scrolling .
Check out this JsFiddle (and scroll with mouse-wheel): https://jsfiddle.net/vb7r1zns/
It seems to happen only when the HTML code starts with another full width/height DIV:
<div id="gjs">
<div style="width: 100%; height: 100%;">
...
What is the expected behavior?
The blue outline should always be exactly matching its parent element, no matter if there is an overflow or scrolling.
Are you able to attach screenshots, screencasts or a live demo?
[x ] Yes (attach) [ ] No
Answers (4)
Would be nice to have this fixed, not the end of the world, but mildly annoying.
any news?
I'm closing this one as it was actually already fixed, indeed the old demo is working now properly. You might still face the issue if your editor is placed in a scrollable container, in that case, use this option please: https://github.com/artf/grapesjs/blob/dc45604962e4e6a4a075f19d5de67090bac15fa5/src/editor/config/config.js#L157-L163
Thanks for reporting this, @fq-selbach.
The issue with the blue outline (gjs-hovered) is not following its parent during scrolling 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 setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
// your operation here
}, 0);
-
Check initialization order — make sure components are fully loaded before you interact with them
-
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.
Issue #5263
Deleting a component without deleting its corresponding style, will adding new components later cause style conflicts?
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? latest version of Chrome Reproducible demo...
Issue #3441
Parser breaks `mj-style` as of 16.30
Version: All Grapesjs version from 16.30 to now have this issues. Are you able to reproduce the bug from the demo?[x] Yes[ ] No What is the...
Issue #3693
AdoptStylesheet not supported in grapesJS
Version: You can get the version by typing grapesjs.version into the console 0.17.22 Are you able to reproduce the bug from the demo?[x] Ye...
Issue #3397
sorter direction incorrect with web component slot
Version:0.16.45 Are you able to reproduce the bug from the demo?[x] Yes[ ] No What is the expected behavior? Given a parent web component i...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins →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.
Tutorial
How to Build a Production GrapesJS Editor: The Complete Walkthrough of Brief, Preset, Plugins, and Services
A complete walkthrough of building a production GrapesJS editor: how to choose a preset, pick plugins, and scope setup services without burning a sprint.
Tutorial
GrapesJS Inline RTE Plugins Update: CKEditor 5 v0.1.4 and Froala Inline Text Editor
CKEditor 5 Inline for GrapesJS v0.1.4 fixes Studio SDK toolbar clipping, iframe injection and link balloon bugs. Compare with Froala Inline — both $69.
Tutorial
Embed GrapesJS in Your SaaS: A Weekend Guide
Embed GrapesJS in your SaaS and ship a white-label page builder over a weekend. Honest tradeoffs, real code, and the plugins that close the UX gap.
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.