GrapesJS Issues

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

220 issues found

๐Ÿ” canvas
#5245Jul 16, 2023by riteshdalal4 answers
0 reactions

Contents of component with editable:false are still editable

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 114.0.5735.198 Reproducible demo link https://jsfiddle.net/riteshdalal/obnx7sg3/22/ Describe the bug How to reproduce the bug?Create a component with editable:false in the modelDrop the component on the canvas What...

artf

The editable property has no meaning by default and it's only used internally by other extended components like Text or Image

riteshdalal

@artf how do we create a component such that gjs does not parse the children.

riteshdalal

The editable property has no meaning by default and it's only used internally by other extended components like Text or Image This used to work on older versions of GJS. Just stopped working in 0.21.3

#5241Jul 14, 2023by hanzuken2 answers
0 reactions

Element absolute position is different from Cursor position when moving in the zoomed canvas

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome version 114.0.5735.199 (Official Build) (64-bit) Reproducible demo link https://grapesjs.com/demo.html Describe the bug How to reproduce the bug?Enable the absolute drag mode editor.editor.set('dmode', 'absolute')Se...

artf

Issues related to Absolute mode are tracked here https://github.com/GrapesJS/grapesjs/issues/3770

GJS Helper

You've accurately identified a common issue in GrapesJS related to absolute positioning and canvas zoom. This is indeed a bug where the drag operation's delta calculation doesn't account for the canvas's current zoom level, leading to a di...

#5229Jul 10, 2023by joukhar4 answers
1 reactions

Textnode with content "null" is rendered as "null" not whitespace

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome Version 114.0.5735.199 (Official Build) (64-bit)Reproducible demo link N/ADescribe the bug How to reproduce the bug?Drop this component <div class=\"flex items-center rounded shadow-md overflow-hidden max-w-xl relativ...

artf

Probably in the first week of August

artf

Hi @joukhar is it happening with the latest version? I'm able to see nulls in the export code if I use your exact JSON example (that should be fixable), but I'm unable to generate those textnodes with nulls by using your HTML example, can...

joukhar

thanks for the replay, if you need demo so please give me some time until i make one , i will comment again when im finished it the problem happens only when u store it and load it, but when u drop the component for the first time nothing...

#5184Jun 14, 2023by acantepie2 answers
1 reactions

Toolbar of ckeditor components is not correctly refreshed

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Version 113.0.5672.126 (Build officiel) (64 bits)Reproducible demo link https://grapesjs.com/demo-newsletter-editor.htmlDescribe the bug How to reproduce the bug?Go on demo website : https://grapesjs.com/demo-newsletter-edit...

artf

Thanks @acantepie please open the issue in the proper repo as this is not core related one

GJS Helper

The issue you're encountering, where the Rich Text Editor (RTE) toolbar in GrapesJS doesn't correctly refresh its state (e.g., bold, italic buttons) when switching between multiple text components, is a known synchronization challenge. Thi...

#5164Jun 6, 2023by shomeel2 answers
0 reactions

By default components are created using table in my demo project but the demo uses flex property to create components

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Version 112.0.5615.49 (Official Build) (x86_64) Reproducible demo link https://jsfiddle.net/shomeelconovo/k7L2rthg/1/ Describe the bug I need help with something regarding the grapes.js. I have created a project and whenev...

artf

https://github.com/GrapesJS/grapesjs/discussions/5163#discussioncomment-6162516

GJS Helper

The difference in default display properties between your GrapesJS project and the official demo stems from the CSS loaded within the GrapesJS canvas iframe, not from GrapesJS itself enforcing display: table or display: flex universally. G...

#5141May 24, 2023by rajevar3 answers
1 reactions

Component resets attribute values on updating traits ( first time only )

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Version 113.0.5672.63 Reproducible demo link https://jsfiddle.net/rajevar/zLs8q97f/4/ Describe the bug This is in reference to this discussion https://github.com/GrapesJS/grapesjs/discussions/4759 How to reproduce t...

rajevar

sorry, my bad. I wasn't using the latest.

artf

@rajevar I can't reproduce it with the latest version, are you sure you're using the latest one?

GJS Helper

You've identified a common synchronization issue in GrapesJS related to how component attributes are managed, especially when classes are modified via the Style Manager and then other traits (like id or title) are updated for the first tim...

#5086May 2, 2023by SagarMaria3 answers
0 reactions

Style:property:update and Property onChange trigger excessively

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Version 112.0.5615.137 (Official Build) Reproducible demo link https://jsfiddle.net/SagarMaria/sunygp2f/3/ Describe the bug How to reproduce the bug?In the jsfiddle simply click on the "Hello World" component. Obser...

artf

The behaviour is correct as style:property:update triggers on any update of the Style Manager Property (not only its value). So for your specific case you would need to update the callback in this way

SagarMaria

Hi @artf, thanks for the quick reply, but actually, part of the problem is still that even after making a change e.g. click "center" align radio option with the if statement you suggested, subsequent selections of that component still log...

GJS Helper

The issue you're encountering with style:property:update and Property onChange firing excessively, even on component selection, is a common point of confusion. The style:property:update event is a low-level event that triggers whenever a s...

#5083Apr 29, 2023by DanavsSite4 answers
0 reactions

Blocks are not draggable to canvas

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Tauri Reproducible demo link Describe the bug How to reproduce the bug?... What is the expected behavior? ... What is the current behavior?** ... If is necessary to execute some code in order to reproduce the bug, paste it...

DanavsSite

DanavsSite

i just found out its because of webview2.Support for webview2??!

artf

I think this is more related to some Tauri configuration instead of GrapesJS as we're using the native HTML5 drag and drop

#4998Mar 22, 2023by glaprida4 answers
0 reactions

ShowOffsetsSelected not working

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chome v111 Reproducible demo link https://codepen.io/glaprida/pen/YzOJOGq Describe the bug How to reproduce the bug?Open the codepen link. Drag any basic block to canvas with some margin or padding.You will see that showOf...

glaprida

Hi, I see that now it works while hovering the element even if it is selected (previously it only worked on non-selected elements) ...but it only shows the offsets while hovering (I thought showOffsetsSelected would show the offsets of the...

artf

Yeah at the moment this is what is intended to do. Probably one day we'll revisit this to make it more customizable (ability to extend/create style handlers on canvas)

glaprida

Hi there, sorry for the insistence... but is there any way you could think of that I can achieve this? What I need is to show the offsets of the selected element, no matter if it's hovered or not.

#4991Mar 21, 2023by glaprida1 answer
0 reactions

Wrong Placeholder marker when dragging a display:grid element

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v111Reproducible demo link https://codepen.io/glaprida/pen/eYLLXbQDescribe the bug How to reproduce the bug?Go to the codepen link https://codepen.io/glaprida/pen/eYLLXbQDrag one section to the canvasDrag another oneW...

GJSBlock

Thanks for reporting this, @glaprida. Great question about Wrong Placeholder marker when dragging a display:grid element. The recommended approach with Canvas is to use the event-driven API. Start here: Check the GrapesJS documentation for...

Browse all topics