Panels "visible" attribute doesn't prevent panel rendering
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?[ ] Yes[x] No 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. Workaro...
Answers (2)
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 :)
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....
Related Questions and Answers
Continue research with similar issue discussions.
Issue #3343
Illegal Invocation error when using keepEmptyTextNodes
Version: 0.16.44 Are you able to reproduce the bug from the demo?[x] Yes[ ] No Set editor.Parser.getConfig().keepEmptyTextNodes = true; in...
Issue #3295
BUG (v0.16.41): Button component with draggable property is not working properly
Version: v0.16.41 Are you able to reproduce the bug from the demo? [ ] Yes [ ] No What is the expected behavior? When we have a button with...
Issue #3166
Problem with copy and paste a node
*Version:0.16.27 Are you able to reproduce the bug from the demo? [ ] Yes [ ] No What is the expected behavior? In the right panel and canv...
Issue #3622
I18n functionality
Version: latest Are you able to reproduce the bug from the demo?[] Yes[ ] No What is the expected behavior? to editor.I18n.setLocale("es")...
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
PageKit: the GrapesJS application you'd have to build anyway
A source-available Next.js app around the open-source GrapesJS core β publishing, custom domains, leads, checkout and a plugin loader.
Tutorial
UnStudio for GrapesJS: 4 Plugins to Build Better Visual Editors
Meet UnStudio, a new GrapesJS plugin studio with four tools, safer and better editor: Command Palette, Responsive Pack, Autosave & Restore, and Autofill
Tutorial
Messaging on gjs.market: talk to a studio before you buy, not after
We've launched private messaging between buyers and studios. One thread per buyerβstudio pair, the whole history in one place.
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.