GrapesJS Issues

artf

@jsxOverdose pushed a fix to this new release: https://github.com/GrapesJS/grapesjs/releases/tag/v0.22.11

jsxOverdose

@artf In the new version, there's another bug: when you click one of the resize handles on the Y-axis, it makes the image significantly larger. Here's the demo: https://jsfiddle.net/du81zL6r/

GJS Helper

The issue you're experiencing with elements jumping to an incorrect position after being moved and then interacting with the resizer is a known behavior related to how GrapesJS handles CSS top and left properties, particularly when positio...

GJS Helper

You've accurately identified a regression in GrapesJS versions 0.22.8 and 0.22.9 where the Layer Manager's visibility toggle from 'invisible' to 'visible' was not functioning correctly. The 'visible' to 'invisible' toggle worked as expecte...

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...

MikeCraig418

For more context, the HTML formatted content disappears from Grapes. The HTML stores strings like:

artf

What Rich Text Editor are you using? Are you able to provide a way to reproduce it (eg. a way I can copy the same text)?

GJS Helper

The issue you're encountering in GrapesJS v1.0.48, where pasting rich content (especially from sources like Microsoft Word) causes attribute values to split into individual attributes, is a known regression. This typically manifests as a s...

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

Thanks for the report @jaredtmartin

GJS Helper

The issue you're experiencing, where blocks do not appear when following the GrapesJS "Getting Started" guide, stems from a misconfiguration in your grapesjs.init options, specifically related to how the blockManager and panels are set up....

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...