GrapesJS Issues

artf

Thanks @FaisalShaikhHA ok I'll fix that as that rule is quite common.

artf

Is it what you see also here https://grapesjs.com/demo.html? I see those icons properly 🤔

FaisalShaikhHA

No, on the demo page icons are visible properly. To update grapesjs I removed the old version by using npm remove grapesjs and then npm install grapesjs to get the latest version. I also tried deleting grapesjs folder from node_modules and...

artf

I guess we should avoid selecting children of already selected components in the first place.

GJSBlock

Thanks for reporting this, @RomanGlazkov. Great suggestion about JS error when moving an element with its child! While this specific feature isn't yet in the core API, there are several ways to achieve similar behavior. Using the event sys...

artf

The script is right above ps: you can use Discussions if you're not reporting a bug

GJSBlock

Thanks for reporting this, @bit-ocean. The issue with A script delcaration mistake at "Commponent & JS" documentation page. appears to be a race condition or state management timing problem. This typically happens when component lifecycle...

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