GrapesJS Issues

trebor94

I've been running into the same issue and also using the grapesjs-mjml plugin. Apparently it only occurs when a project is loaded which has the style property present on the attributes of a component when the project is loaded. After each...

trebor94

Unfortunately haven't been able to figure out where or when exactly the style property gets added to the component style when exporting project data from a previously loaded project. Maybe someone else can pinpoint what causes the issue. @...

GJS Helper

It appears you've encountered a bug in GrapesJS, specifically when working with MJML components and applying styles like padding, which leads to invalid attributes being generated and stored. This issue seems to be a regression, as it work...

GJS Helper

The issue you've described is a known behavioral change introduced in GrapesJS v0.22.10+, where default component styles are incorrectly applied to device-specific media queries when a component is added while a non-desktop device view is...

GJS Helper

The freezing issue you're encountering with your custom Dynamic List component in GrapesJS is a classic example of an event feedback loop. It occurs because the event listener responsible for updating the row count is too broad, causing it...

GJS Helper

You've accurately identified a discrepancy in how the keepEmptyTextNodes option is handled in GrapesJS, leading to newlines being stripped from your HTML output. This is indeed a bug related to the parser's configuration and its TypeScript...

mosh-tudor

@yashvi2026 That's because of your custom CSS code. Remove this part: from editor.BlockManager.add('image', {

artf

I confirm the component resizer doesn't account for !important right now, but I'd follow, more or less, what @mosh-tudor suggested. You don't need to remove the entire styles, as my guess is what you need, but I don't see the point of havi...

yashvi2026

I need to use !important in my style. I've noticed that in other components, when !important is included in the default styles, the styles added through the style manager also include !important to ensure they override the default. So, whe...

GJS Helper

The issue you're encountering, where the "Blocks" panel is still visible despite setting panels: { defaults: [] }, is a common point of confusion. The panels: { defaults: [] } configuration option is indeed designed to prevent GrapesJS fro...

artf

Thanks for the report @tim-prom

GJS Helper

The issue you've encountered, where GrapesJS freezes due to malformed inline styles, is a critical bug stemming from how the editor's internal CSS parser handles invalid syntax, specifically unclosed comments. Root Cause The problem lies i...

artf

Ensure to have this option enabled: https://grapesjs.com/docs/modules/Selectors.html#component-first-selectors

GJS Helper

The issue you're experiencing where resizing one element with a shared class affects all elements with that same class is a known behavior in GrapesJS, stemming from how it manages and applies CSS styles. By default, GrapesJS often tries t...

artf

Thanks for the report @jsxOverdose Will be fixed in the next release

GJS Helper

You've accurately identified a specific behavior in GrapesJS where inline styles appear to completely override ID-based CSS rules, even for non-conflicting properties. This is indeed a deviation from standard CSS specificity rules and can...

GJS Helper

The issue you're encountering with GrapesJS, where repeated rapid creation and destruction of the editor leads to errors like undefined 'allcomponents' and undefined 'lastcomponent', is a classic example of a race condition and state incon...