GrapesJS Issues

iamuddeshya

Facing same issue

deepanshu-ht

++ 1

artf

Just tried the same configuration and all works as expected. Might be related to your grapesjs version or the grapesjs-react itself. Please avoid creating BUG issues if you're not able to provide a reproducible demo with the latest version...

artf

Thanks @AFriboulet-ii I will fix it for the next release.

GJS Helper

The issue you've described is a known behavior in GrapesJS where the undo manager correctly reverts the component's model attributes (including its classes collection), but the ComponentView responsible for rendering the component on the c...

artf

Hi @BenKhz that's happening because selector* events are related to the global Selectors container (when you remove a selector from the component, the Selector itself is still there as it could be used in other places), if you want to trac...

BenKhz

Ah! I was misunderstanding. Thank you for the clarification. Keep up the good work!

GJS Helper

Thank you for reporting this issue and for your kind words about GrapesJS! You've hit upon a common point of confusion regarding GrapesJS events, and it's an excellent question. Root Cause Explanation The selector:remove event, as document...

artf

Unfortunately, as the default implementation relies on the deprecated execCommand, there are too many edge cases to handle and it isn't worth spending time on it anymore. I'd suggest relying on it only for basic formatting (eg. bold, itali...

GJSBlock

Thanks for reporting this, @srinivas977. Great suggestion about Issue with rich text editor Indent action for Lists! While this specific feature isn't yet in the core API, there are several ways to achieve similar behavior. Using the event...

artf

Hi @rajevar I think you're looking for component:create event, as component:add works as expected (eg. might be used to track any new movement inside a specific component)

GJS Helper

You've correctly identified a common point of confusion with GrapesJS event handling. The component:add event indeed triggers not only when a new component is dragged from the blocks panel onto the canvas but also when an existing componen...

artf

The getJs returns the JS of your component model (the one you would place inside model.defaults.script), not the component view. Please read carefully Components & JS

GJS Helper

The issue you're encountering, where editor.getJs({ component }) returns an empty string despite having a submit event handler defined in your custom form component's view.events, is expected behavior and not a bug in GrapesJS. Root Cause...

artf

Please refer to https://github.com/GrapesJS/grapesjs/issues/3515

GJS Helper

The issue you're encountering with the .gjs-selected class not accepting your CSS override is due to GrapesJS's default styling for this class using the !important rule. GrapesJS applies outline: 3px solid #3b97e3 !important; to .gjs-selec...

artf

I think you have to address that to Vite community, the core is using webpack right now and it works as expected

GJS Helper

The error "Uncaught Error: Dynamic require of "codemirror/lib/codemirror" is not supported" arises when you're trying to bundle GrapesJS (or a library that uses GrapesJS) with a modern bundler like tsup (especially when targeting ESM) that...

artf

The error here is using the arrow function, just replace it with clickOnElement() {

GJS Helper

The issue you're encountering with this being window or undefined inside your custom component's view event handler is a common JavaScript this binding problem, especially when using arrow functions. It's not a bug in GrapesJS but rather a...

artf

@wunksert it seems like the editor initializes on itself multiple times, are you properly clearing the editor instance with destroy (eg. in your useEffect)?

wunksert

It might turn out that a fix for this is more simply solved by me editing structure or naming conventions in my project. Happy to do that if it's faster than changing something in GrapesJS core.

artf

yeah definitely not related to the core