GrapesJS Issues

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

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

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

GJSBlock

Thanks for reporting this, @TO-JHummel. Great question about Crash when dragging into nested components with Vue+Vite.. The recommended approach with GrapesJS is to use the event-driven API. Start here: Check the GrapesJS documentation for...

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

GJS Helper

The issue you're encountering stems from how GrapesJS processes and normalizes styles, particularly inline styles, when importing HTML. Let's break down the root cause and provide the correct approach. Root Cause Explanation When GrapesJS...

artf

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

GJS Helper

This is a known issue related to the TypeScript declaration files (.d.ts) in GrapesJS v0.21.1. The problem arises because the type definitions for certain core functionalities, such as Components.addType and the model definition within cus...

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

GJS Helper

The issue you're experiencing, where styles loaded through your Vue.js entry point are lost when GrapesJS initializes, is a common behavior and stems from how GrapesJS isolates its editor canvas. Root Cause GrapesJS, by default, renders it...

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

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.

artf

@ronaldohoch please use the proper documented API

GJS Helper

The issue you're encountering with duplicated elements appearing to lose their parent reference and having an incorrect position stems from how you're trying to access this information. You are relying on view.modelOpt.collection and view....

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.

GJS Helper

The issue you're encountering, where editor.loadData(data, opts) triggers your custom storage's store method, is a common point of confusion but not a bug in loadData itself. The editor.loadData method is designed to import data into the e...