When pasting plain text into text element in Chrome
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?
- Use Chrome and Grapes newsletter Editor
- drag a "Text" element into the page and write something in it.
- In the same element, press "Enter" so you have a new line and paste some plain text
- 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)
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.
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:
- Check the GrapesJS documentation for your specific module
- Look for the
on()event listener method - 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.
Issue #4094
When drag and drop block into editor in Chrome, not able to drag and drop block
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Version 97.0.4692.71 (Official Build) (64-...
Issue #4039
When drag and drop block into editor in Chrome, error thrown
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chromw 96.0.4664.45 Reproducible demo link...
Issue #5689
<> is introduced at the beginning editor.getHtml()
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome Version 121.0.6167.185 (Official Buil...
Issue #5442
After applying the text color not able to set the background color
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? chrome Reproducible demo link https://jsfi...
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
Big Updates: TinyMCE 8 and Placeholder 2.0 for GrapesJS
In May we shipped major updates to two of our most popular GrapesJS plugins — TinyMCE Inline Text Editor and Placeholder.
Tutorial
Find the Right GrapesJS Plugin in Seconds: Smarter Discovery Is Live
We're shipping a set of discovery upgrades. New label filters, a proper compatibility switch for GrapesJS vs Studio, one-click and a smarter sort bar.
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.