GrapesJS Issues

3,464 parsed GitHub issues โ€” 370 solved ยท 90 open. Search, filter and explore battle-tested answers.

466 issues found

๐Ÿ” components
#5674Feb 9, 2024by mauriciolcs22 answers
0 reactions

The infinite canvas is increasing its height infinitely when there is an element with a min-height of 100vh

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Arc version 1.29.0 (46113)Reproducible demo link https://grapesjs-react-custom-ui-vrkhwc.stackblitz.ioDescribe the bug How to reproduce the bug?Enable inifinite canvasAdd at least two components to the canvasSet a min-height...

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

#5668Feb 6, 2024by addlistener2 answers
1 reactions

Sourcemap not loading for CompoentTextView

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Version 121.0.6167.139 (Official Build) (x86_64) Reproducible demo link none. Describe the bug How to reproduce the bug?add customRte and set breakpointsclick step out until it reaches the logic in ComponentTextView What i...

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

#5650Jan 29, 2024by Wayne-Mather2 answers
0 reactions

When inserting text when component not synced, the text is overwritten from the existing model

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Edge 121.0.2277.83, Firefox 122 Reproducible demo link https://jsfiddle.net/50mga1t7/1/ Describe the bug How to reproduce the bug?Create a toolbar action to insert some textEdit a text node and insert some textClick the to...

artf

This is not a bug, merging the current DOM with components requires a bit more effort. There is already a similar API you can use or re-implement with your own needs (using component definition instead of HTML string)

GJS Helper

This is a known synchronization issue between the active ProseMirror editor (which GrapesJS uses for text editing) and the GrapesJS component model. When you're actively editing text in a component, the changes are held within the ProseMir...

#5641Jan 24, 2024by yashvi20262 answers
0 reactions

Undomanager.remove() not working

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v91Reproducible demo link https://codepen.io/Harshsne/pen/WNgZzPEDescribe the bug How to reproduce the bug?Append an image to the canvas and close the image modal.(so that component will be removed from tracking as i...

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

#5633Jan 20, 2024by kla-ko3 answers
0 reactions

Cannot select component in ``component:remove`` handler

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Version 120.0.6099.225 Reproducible demo link https://jsfiddle.net/wattnu/opmwfvjn/ Describe the bug How to reproduce the bug?open and run the fiddletwo components are on the canvas. The "hello world" div and a blue...

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

#5632Jan 20, 2024by Harshsne262 answers
0 reactions

Add a change to the undomanager

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v91 Reproducible demo link https://codepen.io/dhanadsp1120/pen/ExrRvOB Describe the bug How to reproduce the bug? 1.Disable the undo manager by invoking um.stop(). 2.Make alterations to the content. 3.Re-enable the...

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

#5631Jan 19, 2024by Harshsne262 answers
0 reactions

Undo manager add() not working as expected

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v91 Reproducible demo link -- Describe the bug How to reproduce the bug? I wanted to add an change to the undomanager stack . var components = editor.Components; editor.UndoManager.add(components.getComponents().mod...

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

#5630Jan 18, 2024by kla-ko2 answers
0 reactions

Configuring an onStart() resize callback prevents resizing

GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Version 120.0.6099.225 Reproducible demo link https://jsfiddle.net/wattnu/y8L6whun/ Describe the bug How to reproduce the bug?Goto jsfiddlerun the codeon the canvas, select the blue div componenttry to drag the resi...

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

#5618Jan 15, 2024by Ashwinvalento3 answers
0 reactions

Old Component script is not deleted on Import. Resulting in duplicate scripts

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Edge v120.0.2210.121 Reproducible demo link https://codepen.io/ashwinvalento/pen/jOJMPqx Describe the bug If we have set config.parser.optionsHtml.allowScripts: true and create a component with a script, Then when we impor...

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

#5584Dec 27, 2023by vian0132 answers
0 reactions

"storage:end:load" event is not triggered when all components are mounted into the canvas

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v91 Reproducible demo link https://grapesjs.com/demo.html Describe the bug How to reproduce the bug? Recently I have to upgrade grapesjs v0.14.62 to the latest version (0.21.8). In the old code, we used "storage:end...

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

Browse all topics