Issue #3418💬 AnsweredOpened April 27, 2021by emyasnikov0 reactions

Panels "visible" attribute doesn't prevent panel rendering

Quick answerby artf

Yeah, I think it's just a matter of adding this.toggleVisible() in PanelView.render. If you want to push a PR, I'd be glad to merge it :)

Read full answer below ↓

Question

Version:

v0.17.3

Are you able to reproduce the bug from the demo?

What is the expected behavior?

editor.Panels.addPanel({id: 'test', visible: false}) renders panel despite of visible attribute set to false. It perfectly works after editor has been rendered, so panel.set('visibility', !panel.get('visibility') toggles visibility correctly.

Workaround 1 to set gjs-hidden class with visible: false together didn't work too. This way visibility would be checked later and gjs-hidden class would be removed. At least is this the behavior I see.

There was same issue already: #1602.

Workaround 2 to call toggleVisibility function just after panel has been created didn't work too. I think it's because render() function in the PanelView overrides classes. Even to set class manually like it's done in the toggleVisible function didn't work.

What is the current behavior?

Visible attribute is set correctly to false in the panel when I get it using editor.Panels.getPanel('test') but panel itself is still visible until panel.set('visible', false) call after editor has been rendered.

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

Yes (attach)
No

Answers (2)

artf• May 4, 2021

Yeah, I think it's just a matter of adding this.toggleVisible() in PanelView.render. If you want to push a PR, I'd be glad to merge it :)

ClaudeCode• May 17, 2026

Thanks for reporting this, @emyasnikov.

The issue with Panels "visible" attribute doesn't prevent panel rendering 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:

Add a setTimeout wrapper to ensure the DOM has settled:

setTimeout(() => {
  // your operation here
}, 0);

Check initialization order — make sure components are fully loaded before you interact with them
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

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 →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.

Presets Plugins Components Blocks Assets Commands I18n Layers Styles Storages RTE Newsletters Web pages Site builders

Panels "visible" attribute doesn't prevent panel rendering

Question

Answers (2)

Related Questions and Answers

Illegal Invocation error when using keepEmptyTextNodes

BUG (v0.16.41): Button component with draggable property is not working properly

Problem with copy and paste a node

I18n functionality

Paid Plugins That Match This Issue

Related tutorials

How to Build a Production GrapesJS Editor: The Complete Walkthrough of Brief, Preset, Plugins, and Services

Big Updates: TinyMCE 8 and Placeholder 2.0 for GrapesJS

Find the Right GrapesJS Plugin in Seconds: Smarter Discovery Is Live

Browse Plugin Categories