Issue #3455✓ SolvedOpened May 12, 2021by harsh2012 reactions

Style gets wiped out when inserting components in multiple page using Page Manager

Quick answerby artf2

Hi @harsh201 styles are available across all pages, so you shouldn't use editor.setStyle (which replaces all styles with a new set) but instead something like editor.getStyle().add('...')

Read full answer below ↓

Question

Version: 0.17.3

What is the expected behavior? Style should be retained across multiple pages

Describe the bug detailed We have use case where we save and reload the content of GrapesJS. We want to leverage Page Manager to reduce the content rendered and manage it in smaller chunks. The issue pops up when we try to load content in multiple pages. The CSS gets completely wiped out for earlier inserted pages.

Steps to Reproduce

  • Insert components and style for Page 1
  • Switch to Page 2 to and insert components and style.
  • Switch back to Page 1

Current Behavior Style gets wiped out.

Important Snippet From CodePen

const pageManager = editor.Pages;
editor.setComponents('<p id="abcd">TEST Page 1</P>');
editor.setStyle("#abcd {color: #FF00FF}")
pageManager.select('page-2');
editor.setComponents('<p id="efgh">TEST Page 2</P>');
editor.setStyle("#efgh {color: #FFF000}")

Are you able to attach screenshots, screencasts or a live demo?

  • Yes (attach)
  • No

CodePen Demo https://codepen.io/harsh201/pen/VwpepEZ

Answers (3)

👍 Most helpfulartfMay 19, 2021

Hi @harsh201 styles are available across all pages, so you shouldn't use editor.setStyle (which replaces all styles with a new set) but instead something like editor.getStyle().add('...')

harsh201May 19, 2021

Hi @artf, any help here?

ClaudeCodeMay 17, 2026

Thanks for reporting this, @harsh201.

The issue with Style gets wiped out when inserting components in multiple page using Page Manager 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.