Issue #3703πŸ’¬ AnsweredOpened August 13, 2021by anatoli-dp0 reactions

Custom ids have a \3 injected into the css and a space after the following letter after the \3 when added to the canvas

Quick answerby anatoli-dp

please note this issue is bad . . . now that i see it i feel stupid . . . ids cant start with a number and i didnt take that into account when making this

Read full answer below ↓

Question

WARNING

READ and FOLLOW next 3 steps, then REMOVE them before posting the issue

  1. Follow CONTRIBUTING Guidelines https://github.com/artf/grapesjs/blob/master/CONTRIBUTING.md
  2. Do a quick SEARCH first, to see if someone else didn't open the same issue
  3. All relative statements/questions have to be filled/answered, otherwise, the issue might be CLOSED
  4. JSFiddle Starter template https://jsfiddle.net/szLp8h4n
  5. CodeSandbox Starter template https://codesandbox.io/s/1r0w2pk1vl

Version: latest released

You can get the version by typing grapesjs.version into the console

Are you able to reproduce the bug from the demo?

  • Yes
  • No

What is the expected behavior? that if there is a set id and it doesnt match any on the page to leave it alone

Describe the bug detailed a \3 and a space after the character following the \3 is injected into the id . . . for example if i have a css with #testID added as component, the reultant id would end up as "#\3t estID" in the css. the html element is the same just not the resultant css that is created

What is the current behavior?

Describe the bug detailed

Are you able to attach screenshots, screencasts or a live demo? below is images relevant to the issue so if the mistake is on me the sorry (last image is a group of generated ids from generator)

  • Yes (attach)
  • No Screenshot (14) Screenshot (15) Screenshot (16) Screenshot (17)

Answers (2)

anatoli-dpβ€’ August 13, 2021

please note this issue is bad . . . now that i see it i feel stupid . . . ids cant start with a number and i didnt take that into account when making this

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @anatoli-dp.

The issue with custom ids have a \3 injected into the css and a space after the following letter after the \3 when added to the canvas appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.

What to try:

  1. Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
  // your operation here
}, 0);
  1. Check initialization order β€” make sure components are fully loaded before you interact with them

  2. Use the editor's event system β€” listen to completion events:

editor.on('component:mount', (component) => {
  // safe to interact with component here
});

Recommended next steps:

  • Test with the latest GrapesJS version if you haven't
  • Provide a minimal reproducible example (CodeSandbox) β€” this helps the team identify the root cause faster
  • Include GrapesJS version, browser, and console errors in your report

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.