GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? none Reproducible demo link none Describe the bug yarn build fails with two errors: This may just be a problem with TypeScript being too picky, becauseyou may disable the error messages using // @ts-ignore and compile agai...
artf
Thanks @rozek I'll fix it now
rozek
thank you very much!
GJS Helper
Thank you for reporting this issue. You've accurately identified a TypeScript compilation error (TS2532: Object is possibly 'undefined') occurring in the test/specs/utils/Sorter.ts file when running yarn build on GrapesJS commit 4f0c5b1. R...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link https://jsfiddle.net/sdimitrenco/wao1rh0q/30/ Describe the bug That is my components struct If I change the text in the span tag in the text editor, then remove focus from that word, it return...
artf
You shouldn't have "content" inside your text span, indeed if you replace it with "components": "[email protected]", it will work properly.
GJS Helper
The issue you're experiencing, where editable text within a nested span (a text component) inside a link component reverts to its previous state after losing focus, is a known synchronization challenge in GrapesJS when dealing with nested...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Vivaldi Reproducible demo link https://grapesjs.com/demo.html Describe the bug How to reproduce the bug?Press Ctrl+Z after doing an action, to undo itThe action is reversed, but my browser also reopens the last closed tab...
GJS Helper
The issue you're experiencing with Ctrl+Z triggering both GrapesJS undo and the browser's "reopen last closed tab" shortcut is due to the keydown event for Ctrl+Z not having its default action prevented within GrapesJS. While GrapesJS hand...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v114 Reproducible demo link none Describe the bug How to reproduce the bug?I'm using grapesjs-react and using assetManagerMy config looks like this PS: I do have a working endpoint which I've tested already.Now goto...
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...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome V116.0.5845.96 Reproducible demo link https://jsfiddle.net/Adrien_Friboulet/npdkshaf/8/ Describe the bug https://github.com/GrapesJS/grapesjs/assets/128728949/e85b65c4-53ad-43d0-9f5f-74dc0a181dd0 How to reproduce th...
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...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v115.0.5790.170 Reproducible demo link https://jsfiddle.net/BenKhz/yfwqc6mu/1/ Referencing The docs hereDescribe the bugOpen Provided fiddle HereSelect a component on canvas and add a class via the selector manager. (...
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...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome V115Reproducible demo link https://jsfiddle.net/srinivas977/ahgLxv6e/10/Describe the bug How to reproduce the bug? In the provided JSFiddle, include a pair of text lines and select lists. Next, append a sub-list, and...
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...
GrapesJS version 0.21.4[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome Version 113.0.5672.63 Reproducible demo link https://jsfiddle.net/szLp8h4n/11/Describe the bug How to reproduce the bug? Move any of the text components around in the page. An alert will be displayed. could be...
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...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Version 115.0.5790.171 (Official Build) (64-bit)Reproducible demo link https://codesandbox.io/s/1r0w2pk1vl?file=/index.htmlDescribe the bug How to reproduce the bug?... Add this form type and form block What is the expected...
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...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Arc 1.1.1 Reproducible demo link https://jsfiddle.net/3bprucnv/3/ Describe the bug How to reproduce the bug? Add custom css rule for .gjs-selected eg. change the border color to red. .gjs-selected { outline-color: red; } W...
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...