GrapesJS Issues

artf

Yeah thanks @Akira-Kuru fixed the issue here https://github.com/artf/grapesjs-preset-webpage/releases/tag/v1.0.2

GJSBlock

Thanks for reporting this, @Akira-Kuru. Great question about Webpage Demo displaying incorrectly on Firefox. The recommended approach with GrapesJS is to use the event-driven API. Start here: Check the GrapesJS documentation for your speci...

ronaldohoch

Same as described here, not a issue: https://github.com/artf/grapesjs/issues/4350

artf

Yeah but even in a case of a custom UI, the update is skipped if the value is not changed as it's not necessary.

bit-ocean

The code that I pasted is using the standard api, pretty much copy/paste from the documentation. And clearly the update's mechanism has changed between the versions. Before if target element had been changed, the update was triggered, and...

collins-lagat

The release says that there a breaking change. Try that and see if the problem goes away. I got the same error but haven't tried the fix yet. https://github.com/artf/grapesjs/releases/tag/v0.20.1

artf

Yes, as mentioned in the release note you have to switch from the old legacy API for custom component registration.

GJSBlock

Thanks for reporting this, @Aventrue. The issue with After Update to 0.20 from 0.19 the error Cannot assign to read only property 'defaults' of object '[object Object]' occurs appears to be a race condition or state management timing probl...

GJSBlock

Thanks for reporting this, @harsh201. Great suggestion about Textable Component becomes Noneditable when dropped in a Text Block! While this specific feature isn't yet in the core API, there are several ways to achieve similar behavior. Us...

artf

Thanks @wunksert the link is already updated and will be fixed on the next release

GJSBlock

Thanks for reporting this, @wunksert. Great question about API Docs Configuration Object link broken. The recommended approach with GrapesJS is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific mod...

artf

Yeah, you're right, I'll fix it, thanks for the report.

GJSBlock

Thanks for reporting this, @Singwai. The issue with Resizer cursor's starting position should also use the mousePosFetcher if provided. appears to be a race condition or state management timing problem. This typically happens when componen...

artf

Sure, I'll add it, thanks for the suggestion.

GJSBlock

Thanks for reporting this, @Singwai. The issue with Resizer onEnd callback should include the resizer and el object similar to onStart appears to be a race condition or state management timing problem. This typically happens when component...

artf

You can use Discussions if you have questions, Issues are only for reproducible bugs

GJSBlock

Thanks for reporting this, @joukhar. Great question about prevent event using custom plugin. The recommended approach with GrapesJS is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific module Look...

artf

RTE relies on the DOM content during the editing so if you remove it deliberately with something like inner components will be removed once the editing is finished.

benryanwilliams

Ok thanks @artf, that makes sense. However, those lines of code, along with are required to render the correct selected state inside the canvas as follows (both upon the component initially being rendered and when the user selects a differ...

benryanwilliams

I need to do some more testing but it looks like I've got around this behaviour by saving the inner components inside the component itself when first creating it / editing it, then using the rte:disable hook as follows: It seems a bit hack...

Singwai

Feel free to update the type definition, here is an example commit. https://github.com/artf/grapesjs/commit/49deeeeab74aff3e46f22d0bb06e7f7608955afd

Aventrue

My workaround: let assetConfig: grapesjs.AssetManagerConfig = {}; assetConfig["custom"] = { open: (props) => { this.openGalleryDialog(props); }, close: (props) => { this.dialog.closeAll(); }, };

GJSBlock

Thanks for reporting this, @Aventrue. The issue with Custom is missing in the AssetManagerConfig appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modification...