GrapesJS Issues

artf

Yeah, the editor instance is not expected to be destroyed immediately due to some deferred async functions (eg. for the StorageManager) but that can be fixed. For now you can overcome the issue by doing something like this:

GJSBlock

Thanks for reporting this, @mani-rai. Great question about Destroying and re-initializing produces "Cannot read properties of undefined (reading 'get')". The recommended approach with ProseMirror is to use the event-driven API. Start here:...

artf

Read carefully this guide, everything inside script is outside of the editor scope. You can update the component itself by using component.components method or specify the components: '<div ....' directly in definition.

GJSBlock

Thanks for reporting this, @panditlakshya. Great question about Grapesjs fails to recognize component types when setting innerHTML through script.. The recommended approach with Canvas is to use the event-driven API. Start here: Check the...

artf

This is expected due to some logic related to the rich text editor. You can use component.getInnerHTML() to get the inner HTML or component.components() to get inner components.

GJSBlock

Thanks for reporting this, @NicoGGG. Great question about Component content is set to empty string after inline editing. The recommended approach with Canvas is to use the event-driven API. Start here: Check the GrapesJS documentation for...

artf

Seems to be related to CssGroupRuleView here. In case of at-rules like @keyframes we have to force the re-render of the parent container.

wunksert

@artf facing this issue again with editor.CssComposer.remove(myCssRule) the editor css removes the rule but it's not flushed through to the DOM. How to you recommend I force re-render of the DOM while keeping the state of my editor intact?...

GJSBlock

Thanks for reporting this, @wunksert. Great question about Css edits aren't persisted to the DOM. The recommended approach with StyleManager is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific mod...

artf

hey @bgrand-ch I think one day all grapesjs entities will have a global uid, so in long-term, I'd expect this issue to be fixed 🤞

quentin-bettoum

At first, I wanted to generate all the pages together to have a single CSS output for all the pages. But now I'm trying another solution for the styles. So for the id problem, generating each page separately could be a solution. Thanks for...

bgrand-ch

Grapes to use some data attributes (something like data-grapes-id) as unique identifiers to leave the id free for some frontend scripts. I like this idea 💯

ronaldohoch

I just came here to open the same issue! :( @artf, you can add this code to check it.

artf

Reported and fixed here

GJSBlock

Thanks for reporting this, @henry-mmw. The issue with GrapesJS doesn't understand '@-webkit-keyframe' CSS rules. appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and...

artf

Oh yeah, that should be removed, thanks.

GJSBlock

Thanks for reporting this, @quentin-bettoum. Great question about _undoexc status open. The recommended approach with ProseMirror is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific module Look fo...

derciesto

@jasonliang-dev any update on this? i facing same issue.

GJSBlock

Thanks for reporting this, @jasonliang-dev. Great question about Closing </script> tag not escaped for script properties. The recommended approach with StyleManager is to use the event-driven API. Start here: Check the GrapesJS documentati...

artf

You should still be able to use the escapeName option

GJSBlock

Thanks for reporting this, @hemaltandel1. Great question about css class name with '/' converted to '-'. The recommended approach with Canvas is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific mo...

GJSBlock

Thanks for reporting this, @dreamsight. The issue with * appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent stat...