GrapesJS Issues

artf

Avoid using infinite canvas as it was never documented and not even finished as a feature.

GJS Helper

The issue you're encountering with the GrapesJS infinite canvas increasing its height infinitely when an element with min-height: 100vh is present is a known interaction problem between CSS viewport units (vh) and the dynamic resizing mech...

artf

The problem here is not Undomanager.remove but what is tracked. When you're resizing the image, you're not editing the Component itself but its CssRule object so that's why it's not working as expected. I'd probably suggest to simply skip...

GJS Helper

The issue you're encountering with editor.UndoManager.remove() not preventing the undo of a component's removal is due to a misunderstanding of how the UndoManager operates in this specific context. The UndoManager.remove(component) method...

artf

Thanks @kla-ko there is actually one logic that prevents selecting other components during component:remove events and I will fix it for the next release but what I'd suggest to you is to switch to another event. The event component:remove...

kla-ko

Thanks @artf . This works like a charme ! /

GJS Helper

The issue you're encountering where editor.select() doesn't work as expected within the component:remove handler is due to the timing of the event and GrapesJS's internal component lifecycle. The component:remove event fires before the com...

artf

Good catch, will fix it

GJS Helper

The issue you're encountering where configuring an onStart callback for the resizable property prevents the component from being resized is due to how GrapesJS (and often underlying drag/resize libraries) handles custom event callbacks. Wh...

artf

Reimporting directly JS as a component was never possible, so it's treated as a new one.

Ashwinvalento

Is there any way we can identify scripts of existing components and delete them on import? we wont be able to remove all the script tags since we would need to retain the scripts added manually.

GJS Helper

The issue you've encountered with script duplication when importing HTML multiple times in GrapesJS, especially with config.parser.optionsHtml.allowScripts: true, is a known behavior related to how GrapesJS reconciles components during set...

artf

Good catch, I'll fix it

GJS Helper

This is a known bug in GrapesJS related to how the Layers panel (specifically the Layer view) reacts to changes in a component's children collection. The issue arises when a component, like a column or cell, is initially empty and then has...

artf

Thanks for the report @thigh will fix it

sunnynk19

Hi @thigh, Looks like still not working. Have you deployed the latest npm package?

artf

Not yet published, you can find here all the releases https://github.com/GrapesJS/grapesjs/releases

artf

@vian013 please open bug issues only with a reproducible demo link, by a quick check the event seems to work properly

GJS Helper

The change in behavior for the storage:end:load event in GrapesJS from version 0.14.62 to 0.21.8 is intentional and reflects a more granular event system. In newer versions, storage:end:load is triggered specifically when the data has been...

GJS Helper

The behavior you're observing with script tag attributes not appearing on the GrapesJS canvas, while being present in the exported HTML, is expected and by design for how GrapesJS handles non-visual elements, especially script tags carryin...

GJS Helper

You've accurately identified a minor, yet unexpected, behavior in GrapesJS where the rte:disable event is triggered when dragging a new component (like a text block) from the blocks panel onto the canvas. This is indeed not the expected be...