GrapesJS Issues

Search parsed GitHub issues, see highlighted answers, and open the original discussion when needed.

3464 issues found

#5086May 2, 2023by SagarMaria2 answers
0 reactions

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

#5083April 29, 2023by DanavsSite3 answers
0 reactions

BUG: 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

#5079April 28, 2023by TO-JHummel1 answer
0 reactions

BUG: Crash when dragging into nested components with Vue+Vite.

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefox 112.0.2 (64-Bit) Reproducible demo link https://github.com/TO-JHummel/grapesjs-issue Describe the bug How to reproduce the bug?Start the minimal vue+vite page.Drop the capitalizedfor block into the editor.Drop the...

artf

This is similar to this one, you have to put the editor instance outside of the Vue instance in order to bypass its proxies

#5059April 19, 2023by abubaker4171 answer
0 reactions

BUG: on second-time use template grapes editor not accepting css which the editor created with random ids on the first time

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Version 111.0.5563.147 (Official Build) (64-bit) Reproducible demo link I can't Reproducible on jsfilddle. i provided detail below. Describe the bug How to reproduce the bug?This is my template which I uploaded in Grapes i...

artf

@Spiral1234 if you're not able to reproduce the issue it's probably something on your end and without a reproducible demo it's hard to understand what might be a problem

#5053April 17, 2023by ngoc1991 answer
1 reactions

BUG: types are changed to `any` in v0.21.1

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? FireFox 112.0 (64-bit) Reproducible demo link No demo link Describe the bug I recently upgraded from v0.20.1 to v0.21.1. A lot of types that existed in v0.20.1 are changed to any in v0.21.1. For example, Type of Components...

artf

Thanks @ngoc199 please let me know if there are others missing declarations from the previous versions

#5052April 16, 2023by innothetechgeek1 answer
0 reactions

Styles loaded through vue entry point not working

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link N/A Describe the bug I'm integrating the grape.js plugin with vue.js. I have a prebuild page with prebuild html and css. When I load the page vue.js component(s) into the editor, all my vue.js...

artf

@innothetechgeek for a proper bug issue you should always create a reproducible demo as commonly there are issues unrelated to the core itself. Anyway, from your description you might want to define your styles entry via canvas options

#5049April 13, 2023by ronaldohoch3 answers
2 reactions

BUG: Problem when dragging component composed by image and link

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Brave last version Reproducible demo link https://jsfiddle.net/rp7oc96v/1/ Describe the bug Hi Arthur! I'm creating a new component, an image inside a link, like the mj-image component, but i'm stuck in one configuration o...

gustavohleal

Hi! I've tested your solution. It does change the image correctly with the image locked inside the main component and you can move it around. The src attribute is changed in the model, but when you move the component he goes back to the pl...

artf

@gustavohleal my bad, you have to update the src property directly instead of the attribute image.set({ src: asset.getSrc() });

artf

Use the data-gjs-locked="true" property to ignore the image and update properly your custom component

#5046April 12, 2023by abubaker4173 answers
0 reactions

BUG: is there any way to remove cross svg on selected default value of Float, Position and text-align

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Version 111.0.5563.147 (Official Build) (64-bit) Reproducible demo link https://grapesjs.com/demo.html Describe the bug How to reproduce the bug? this is the image link where you can check https://ibb.co/0Qg7nTK What is th...

artf

@Spiral1234 there is a big difference between a default value and the defined one (even if it's the same as default). For example on desktop you define float: right and on mobile float: none, you still need the possibility on mobile to rem...

abubaker417

@artf, let me define you one more time. My question is that if I click on the default value of any module like for float I select `none then cross svg should be display: none same as I want for others position, text-align if someone will s...

artf

@Spiral1234 it shouldn't be display: none if you SELECT the default value, try to read carefully again the use case explained above, having the default value and selected one is DIFFERENT.

#5045April 12, 2023by ronaldohoch1 answer
1 reactions

BUG: Duplicate elements lost the parent element reference

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Brave last versionReproducible demo link https://grapesjs.com/demo.htmlDescribe the bug How to reproduce the bug?Drop an image. Select the droped image.Run the code above.Duplicate the imageSelect the droped image.Run the co...

artf

@ronaldohoch please use the proper documented API

#5042April 11, 2023by pittleCheung1 answer
0 reactions

BUG: Every time editor.loadData(data, opts) is called, it triggers the store method defined in editor.Storage.add("api-remote", {...}), which logs the message 'api-remote store'

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? latest version of Chrome Reproducible demo link null Describe the bug How to reproduce the bug? it's easy What is the expected behavior? I want to use editor.load to load data and switch pages, but I don't want editor.Stor...

artf

You can update dynamically stepsBeforeSave in order to avoid triggering the store on Storage call. Please next time use Discussions as this is not a bug but implementation question.