GrapesJS Issues

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

There was an issue with the demo itself which now it's fixed (added draggable: false to the wrapper component)

FaisalShaikhHA

Patch for getCss to return always the content from the editable component is not working, can you please help me to solve this @artf The below code (present in the reproducible demo link) always returns the whole canvas or wrapper CSS stri...

GJSBlock

Thanks for reporting this, @FaisalShaikhHA. Great question about Component with pointer-events: 'all' (except wrapper) or editable component are draggable & droppable to itself.. The recommended approach with StyleManager is to use the eve...

artf

You should already be able to achieve the same effect with the default transform property, your custom one is not complete. Try to reference the complete configuration here. In case you want to update properties, you should be able to exte...

GJSBlock

Thanks for reporting this, @ronaldohoch. Great suggestion about Transform scale and rotate don't work properly.! While this specific feature isn't yet in the core API, there are several ways to achieve similar behavior. Using the event sys...

GJSBlock

Thanks for reporting this, @JonathanRiche. Great question about stylePrefix property not overiding the gjs in most elements with the gjs-class. The recommended approach with StyleManager is to use the event-driven API. Start here: Check th...

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

artf

This first one is the component method, the second is the block property (used here)

vaneatka

the reason I opened this issue is that the method is not visible. maybe there is need to a new entry for the method declaration in the types? like for the setId /*Set new id on the component / setId(id: string): this;

GJSBlock

Thanks for reporting this, @vaneatka. Great question about resetId types mismatch. The recommended approach with Components is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific module Look for the...

artf

This is not related to the core but more to the Tab plugin which is not re-importable by default.

Rilvatore

Hey! Thanks a lot for the answer. In fact, the issues seems to come from the reimport code & store manager, that does not update the JSON part of the code. Would you have a way to take a look? Or should we create the same ticket on the tab...

artf

It's related to the Tab plugin as once you print its HTML there is no way to reimport is back. You can actually extend the Tab component and add the isComponent method to allow the parser to identify the component.

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

GJSBlock

Thanks for reporting this, @ronaldohoch. Great question about Strange behavior when trying to change color of buttons and texts. The recommended approach with StyleManager is to use the event-driven API. Start here: Check the GrapesJS docu...

GJSBlock

Thanks for reporting this, @PaulSchult. Great suggestion about Angular Component as Custom Color Picker is only created once! While this specific feature isn't yet in the core API, there are several ways to achieve similar behavior. Using...