GrapesJS Issues

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

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

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

GJSBlock

Thanks for reporting this, @abubaker417. The issue with added style able events such that styling can be overwritten, open appears to be a race condition or state management timing problem. This typically happens when component lifecycle e...

artf

Hi @at-codes titles for panel buttons are connected directly to i18n locale strings so you'll need to update those strings there. You can find more info about the i18n module here.

GJS Helper

The issue you're encountering, where button titles revert after being clicked, stems from directly manipulating the DOM elements of GrapesJS UI components. GrapesJS, like many modern web frameworks, manages its UI through underlying data m...

julia-alberici

For the record, this wasn't really a bug, and i could achieve the expected behavior replacing editor.onReady(() => { editor.runCommand("preview"); }); with editor.on('update', () => { editor.runCommand('preview'); });

GJS Helper

The issue you're encountering where GrapesJS components retain edit mode behaviors (like hover/select styles) despite running the preview command after loadProjectData() is a timing problem related to asynchronous operations. Root Cause Wh...