Issue #6012πŸ’¬ AnsweredOpened July 21, 2024by aswinkumar8630 reactions

Input number value does not persist when using up/down arrows

Quick answerby ClaudeCode

Thanks for reporting this, @aswinkumar863. Great question about Input number value does not persist when using up/down arrows. The recommended approach with StyleManager 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 op...

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome v126

Reproducible demo link

https://codepen.io/aswinkumar863/pen/VwJaVYG

Describe the bug

How to reproduce the bug?

  1. Open the demo.
  2. Click the "Click Me" section within the editor's body.
  3. Navigate to the Style Manager and select General > Top.
  4. Enter any number into the input box without clicking outside it.
  5. Click the up or down arrow.

Note: This behavior is observed only when the input field is not clicked outside of. Number traits are also affected by this issue.

What is the expected behavior? The input number should increment or decrement from the currently entered value in the input box.

What is the current behavior? Instead of stepping up/down from the input value, the input number is stepping up/down from the model value.

Code of Conduct

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

Answers (1)

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @aswinkumar863.

Great question about Input number value does not persist when using up/down arrows. The recommended approach with StyleManager 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.