GrapesJS Issues

JonathanRiche

needed to run visualEditor.stopCommand('sw-visibility') first not sure if this is new runCommand used to toggle before with having to run stop

GJS Helper

Thank you for reporting this issue. I've investigated the behavior of editor.runCommand('sw-visibility') on the latest GrapesJS demo page (https://grapesjs.com/demo.html) and found that the command does work as expected. When executed in t...

artf

Provide valid reproducible demo

GJS Helper

The issue you're encountering where a <td> element changes its display behavior (appearing as a table-row or table-body) when float: right or float: left is applied is not a bug specific to GrapesJS. Instead, it's a fundamental behavior of...

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

I can only suggest to check properly the source map path <img width="346" alt="Screenshot 2024-02-12 at 08 45 32" src="https://github.com/GrapesJS/grapesjs/assets/11614725/ee135460-a758-4aef-96fa-1d1b463c934d"> For example, it won't work i...

GJS Helper

It appears you're encountering an issue where the sourcemap for ComponentTextView isn't loading in your browser's DevTools, even though RichTextEditorModule's sourcemap seems to be working. This is a common point of confusion when debuggin...

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

When the undo manager resumes, any modifications made after its pause should be treated as a single change. This ensures that clicking "undo" will revert the entire set of alterations to the state prior to the undo manager's interruption....

GJS Helper

The issue you're encountering is expected behavior for the GrapesJS UndoManager. When um.stop() is called, the UndoManager ceases to listen for editor changes. Consequently, any modifications made during this period are not recorded in its...

artf

@Harshsne26 you need to provide a reproducible demo for a bug

GJS Helper

The issue you're encountering with editor.UndoManager.add() not working as expected stems from a misunderstanding of the method's intended use and the type of argument it expects. The GrapesJS UndoManager is designed to track changes to th...

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

ronaldohoch

https://github.com/GrapesJS/grapesjs/pull/5622

GJS Helper

You've accurately identified a visual bug in GrapesJS related to how the placeholder for empty elements is positioned when the element has a significant border. This behavior is reproducible in the GrapesJS demo and affects the user experi...

GJS Helper

You've accurately identified a type definition inconsistency in GrapesJS. The issue stems from a mismatch between the declared type for StyleManagerConfig.sectors.properties in src/stylemanager/config/config.ts and its actual usage and int...