GrapesJS Issues

CaptSadaf

cc: @jcamejo @artf

artf

Those actions are only available for the built-in RTE, if you replace it with a custom RTE like CKEditor you don't see them. You have to use CKEditor itself for your custom logic.

GJS Helper

The issue you're encountering stems from a fundamental difference in how GrapesJS's default Rich Text Editor (RTE) and CKEditor handle toolbar customizations. When you enable grapesjs-plugin-ckeditor, GrapesJS replaces its lightweight, bui...

artf

Thanks @c9a2334 would you like to contribute on this fix?

GJSBlock

Thanks for reporting this, @c9a2334. Great question about Missed localization keys for de locale. The recommended approach with GrapesJS is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific module...

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

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

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

Thanks @skru yes, there is an internal issue I have to fix to properly handle extended text components but once it's fixed another thing to keep in mind when you extend text components, it's to use components property instead of content.

GJSBlock

Thanks for reporting this, @skru. Great question about Extending text component breaks textable blocks. The recommended approach with Components is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific...

GJSBlock

Thanks for reporting this, @m-jojo-s. Great question about Unable to move editable text cursor on touch. The recommended approach with GrapesJS is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific...

artf

Sorry but this is not a bug, it simply doesn't work that way. Anyway refer always to the latest documentation https://grapesjs.com/docs/modules/Components-js.html#passing-properties-to-scripts as this method of passing properties was depre...

GJSBlock

Thanks for reporting this, @bimsina. Great question about Can't parse trait values using Template literals(String Interpolation). The recommended approach with Components is to use the event-driven API. Start here: Check the GrapesJS docum...

GJSBlock

Thanks for reporting this, @Merorh. Great question about Uncaught TypeError: Cannot read properties of null (reading 'ownerDocument'). The recommended approach with Keyboard is to use the event-driven API. Start here: Check the GrapesJS do...