Issue #4861πŸ’¬ AnsweredOpened January 21, 2023by edenizk1 reactions

<br/> is adding to single line text, after entering space for the first time in firefox

Quick answerby artf❀ 1

Unfortunately this is not related to grapesjs itself but how Firefox handles editable text. I guess one option would be to switch to some custom rich text editor which doesn't rely on the native behaviour.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Firefox

Reproducible demo link

https://jsfiddle.net/8rm5wv2y/1/

Describe the bug

How to reproduce the bug?

  1. open example page in firefox (it has no modification)
  2. click show code, you will see that there is no <br/> element inserted
  3. press space after "Hello World!!!" if you want you can add any text
  4. click show code again, you will see that after your new added text you will have <br/> element added

What is the expected behavior? If the user is not pressing enter or shift+enter, but writing on single line I would like to not to get <br/> element. Like in the chrome.

What is the current behavior? when ever user is adding text to existing text, grapes is adding <br/> element in firefox.

Code of Conduct

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

Answers (3)

artfβ€’ January 23, 2023

Unfortunately this is not related to grapesjs itself but how Firefox handles editable text. I guess one option would be to switch to some custom rich text editor which doesn't rely on the native behaviour.

edenizkβ€’ January 23, 2023

Thank you for your answer πŸ™‚

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @edenizk.

Great question about <br/> is adding to single line text, after entering space for the first time in firefox. The recommended approach with ProseMirror 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.