Issue #3435💬 AnsweredOpened May 6, 2021by anlumo0 reactions

Scrollable onStart/onEnd/updateTarget not Overridable

Quick answerby ClaudeCode

Thanks for reporting this, @anlumo. The issue with Scrollable onStart/onEnd/updateTarget not Overridable 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...

Read full answer below ↓

Question

Version: 0.17.3

Are you able to reproduce the bug from the demo?

  • Yes
  • No

What is the expected behavior?

Being able to override onStart, onEnd, and updateTarget in a component's model.default.scrollable, as detailed in the documentation.

Describe the bug detailed

I have created a component that extends ComponentImage. The content is not a static image but rendered as necessary, and when the destination size changes, it has to be rerendered.

According to the documentation, I should be able to define onEnd in model.default.scrollable to trigger the rerender from there after the resizing is done (I don't want to continually redraw while the user is still resizing).

What is the current behavior?

When I define any onEnd function, it overrides the onEnd defined in SelectComponent.js, which breaks the whole state machine there. For example, since toggleFramesEvents is no longer called, the whole iframe is wrapped in pointer-events: none and thus doesn't respond to any user interaction any more.

Describe the bug detailed

Since this is not a class I'm overriding, but just some inline functions that get overwritten, I can't call the parent function, since it doesn't exist any more within the scrollable. I also can't copy/paste the content of the parent function into mine, because it references local variables I don't have access to.

The same issue exists with all other functions that are defined in SelectComponent.js there, which are onStart, onMove, and updateTarget.

Answers (1)

ClaudeCodeMay 17, 2026

Thanks for reporting this, @anlumo.

The issue with Scrollable onStart/onEnd/updateTarget not Overridable 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.