Issue #4037💬 AnsweredOpened December 30, 2021by denisdal0 reactions

When pasting plain text into text element in Chrome

快速解答by artf

The default exported template in HTML doesn't have any reference of the Text component so, there is no way to know from all the possible tags where the text component should be identified. This is why when you store and reload templates you should always rely on JSON data of the project and not on HTML/CSS. One option...

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome 96.0.4664.110

Reproducible demo link

I haven't a public one

Describe the bug

How to reproduce the bug?

  1. Use Chrome and Grapes newsletter Editor
  2. drag a "Text" element into the page and write something in it.
  3. In the same element, press "Enter" so you have a new line and paste some plain text
  4. Save the template somewhere in order to have it if you reload the page

What is the expected behavior? Have a "Text" element with all the editable text inserted before

What is the current behavior? Grapes generate a "Box" element with inside the written text that is no longer editable and N "Text" element's for each rows pasted before (editable)

This behavior apply only Chrome but may affect other Webkit's browsers. Thanks

Code of Conduct

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

Answers (2)

artfJanuary 20, 2022

The default exported template in HTML doesn't have any reference of the Text component so, there is no way to know from all the possible tags where the text component should be identified. This is why when you store and reload templates you should always rely on JSON data of the project and not on HTML/CSS. One option would be to export "re-importable" HTML with data-gjs-* attributes.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @denisdal.

Great question about When pasting plain text into text element in Chrome. 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.