Issue #3779💬 AnsweredOpened September 15, 2021by stljeff10 reactions
questioncomponentsbugtypescript

Editor.getSelected().toHTML() encodes inline javascript

Quick answerby artf

You have to use allowScripts And I see no issues with encoding (use the real inspector, not the jsfiddle beta console, which probably has a bug).

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

latest (chrome)

Reproducible demo link

https://jsfiddle.net/4j1k0wde/24/

Describe the bug

How to reproduce the bug?

  1. create block with a script tag inside.
  2. use editor.getSelected.toHTML() to grab the block's markup (so user can edit that block's markup in a popup dialog)

What is the expected behavior? ... I get the block's HTML, including the script tag and it's contents

What is the current behavior? ... Either no script tag or the special characters are encoded.

Further info here: https://github.com/artf/grapesjs/discussions/3776

Using version 16.12, toHTML() works as expected. I get all the contents of my selected component, including the script tags with its original javascript intact.

using newer versions of GrapessJS (on my machine, in my app), toHTML() returns script tags with the javascript encoded like so: const form = document.getElementById('91003');

In the JSFiddle I created, the script tag isn't even returned by toHTML.

RE: My JSFiddle - I understand the way I am adding my Edit button to my component's toolbar is convoluted. I am dealing with a legacy app with a bunch of hack-ish things going on. Still, why should that affect the toHTML() function call?

Thanks for your attention.

Code of Conduct

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

Answers (3)

artf• September 16, 2021

You have to use allowScripts

const editor = grapesjs.init({
  ...
  allowScripts: true,
});

And I see no issues with encoding (use the real inspector, not the jsfiddle beta console, which probably has a bug).

stljeff1• September 22, 2021

Thank you!

ClaudeCode• May 17, 2026

Thanks for reporting this, @stljeff1.

Great question about editor.getSelected().toHTML() encodes inline javascript. The recommended approach with Components 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.

Issue #5724

Whitespace handling in inline elements

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v122Reproducible demo link https://js...

2 answersUpdated September 10, 2024

Issue #3873

Duplicated video block when re-attaching GrapesJs editor to document

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v94 Reproducible demo link https://...

3 answersUpdated October 20, 2021

Issue #6603

Ampersand is not escaped in attribute value

GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v142.0.7392.0 (canary) Reproducible...

2 answersUpdated September 12, 2025

Issue #6409

Cannot drag to move components on mobile

GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v133 Reproducible demo link https:/...

4 answersUpdated June 23, 2025

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 →

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.

Tutorial

GrapesJS vs Webflow vs Tilda: What to Choose for Your Business in 2026

Choosing the right website platform in 2026 is no longer just about building a site

Tutorial

GJS Market 2.0 - Donations, Tracking, Labels and Better Product Discovery

We’ve rolled out a new set of GrapesJS marketplace updates across GJS Market, focused on improving how creators distribute products

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.

PresetsPluginsComponentsBlocksAssetsCommandsI18nLayersStylesStoragesRTENewslettersWeb pagesSite builders