[BUG] Default styling not being applied when default panels are instantiated
Question
It seems that when the default panels is altered in the config, the basic styles are stripped from the panels. For example the font and scrollbars.
-
Are you using the latest release (older versions are NOT supported)? Yes
-
Are you facing the bug with your local copy of GrapesJS or with the current demo? Both
-
What is the expected behavior? When a
defaultpanel is added, that overflow scrolling and stylings consistent with the rest of the editor -
What happens instead? Stylings are not applied to the panel
Live example: https://jsfiddle.net/bhujavo5/
It's weird because the default styling is applied to the canvas, but is rejected from the rest of the editor. Am I incorrectly initializing the editor?
Answers (3)
Sorry @adriangroch but I don't really understand what do you expect. I see the panel and its styles correctly applied. Are you talking about the scroll outside the editor?? That has nothing to do with the editor and its styles...
@artf, when you have enough components on the canvas and then select the layer manager, the styles are not applied as they are in the default example - the font is different and the scrollbar has changed. It's all still within the editor

That scrollbar is not from the editor but from the body and about the font, being a custom UI (when you use appendTo) the font is taken from the parent
Related Questions and Answers
Continue research with similar issue discussions.
Issue #2722
[BUG] Highlight and toolbar positioned wrong on outside scroll
Are you using the latest release (older versions are NOT supported)? Yes Are you facing the bug with your local copy of GrapesJS or with th...
Issue #2683
[BUG] When cancel Colorpicker, it set wrong value for component
Are you using the latest release (older versions are NOT supported)? Yes.Are you facing the bug with your local copy of GrapesJS or with th...
Issue #2469
[BUG] Adding buttons to RTE toolbar in React App causes buttons to be duplicated.
Are you using the latest release (older versions are NOT supported)? YES, 0.15.9Are you facing the bug with your local copy of GrapesJS or...
Issue #1411
Manual triggering of the asset manager rendering is required after opening the AM pop-up
Questions Q: Are you using the latest release (older versions are NOT supported)? A: Yes Q. Are you facing the bug with your local copy of...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.