GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 114.0.5735.198 Reproducible demo link https://jsfiddle.net/riteshdalal/obnx7sg3/22/ Describe the bug How to reproduce the bug?Create a component with editable:false in the modelDrop the component on the canvas What...
artf
The editable property has no meaning by default and it's only used internally by other extended components like Text or Image
riteshdalal
@artf how do we create a component such that gjs does not parse the children.
riteshdalal
The editable property has no meaning by default and it's only used internally by other extended components like Text or Image This used to work on older versions of GJS. Just stopped working in 0.21.3
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome Version 114.0.5735.199 (Official Build) (64-bit)Reproducible demo link N/ADescribe the bug I'm sorry for opening the issue again, but your commits doesn't work i installed dev version using npm install GrapesJS/grapes...
artf
@joukhar npm install GrapesJS/grapesjs#dev is not enough, I didn't create the build in the dev branch yet, so if you want the fix locally you have to build it yourself first. Anyway, there is no need to create new issue even if the related...
GJS Helper
Thank you for reporting this issue and providing detailed insights into the relevant code sections. You've correctly identified the root cause of the problem. Root Cause Analysis: The issue stems from how JavaScript's textContent property...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? 114.0.5735.133 Reproducible demo link Impossible to add a worker to reproduce. Describe the bug How to reproduce the bug?Add a web worker.Initialize GrapesJS with "headless" option inside the worker.Add a plugin with "edit...
artf
Hi @bgrand-ch unfortunately everything that involves the parser (HTML/CSS) requires the DOM related API to be available. For the CSS maybe you can try to use parser-postcss plugin, I'd expect it to work in the worker environment
bgrand-ch
Hi @artf, thanks a lot for your quick answer ๐ I will try this week.
bgrand-ch
@artf The Post CSS parser plugin works perfectly in a web worker! Thanks for your help.
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Safari 16.5Reproducible demo link https://grapesjs.com/demo.html https://staubgeborener.de/Describe the bug I was trying out the official demo. I changed nothing, but simply click the view code button and download the html a...
artf
This is not related to the core but simply a missing meta tag in the exported HTML from the demo.html If you want to submit a PR I'll be happy to merge it there
GJS Helper
The issue you're experiencing is not a bug in GrapesJS itself, but rather a common oversight when deploying responsive web pages. The root cause is the absence of the viewport meta tag in the <head> section of your exported HTML file. Root...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? v9.2 Reproducible demo link https://jsfiddle.net/szLp8h4n Describe the bug I am using it in vue3 project when I want to add new components , page is hanged and not response this is my code : Code of Conduct [X] I agree to...
gxanshu
Hi there! ๐ I don't believe this is a bug with GrapesJS. I checked your reproduction link and tried adding a component to the canvas, and it worked perfectly fine for me without any issues. ๐
artf
You have to bypass Vue's Proxy observers https://github.com/GrapesJS/grapesjs/issues/4497#issuecomment-1213078160
GJS Helper
The issue you're encountering, where the page hangs when programmatically adding new components, stems from an incorrect approach to component creation and attachment within GrapesJS. You're essentially trying to add a component that is al...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link https://codesandbox.io/s/adoring-margulis-873kdv Describe the bug Context Move component method doesn't work as expected. This piece of code doesn't work as expected. this piece of code should...
krishnaeverestengineering
Fix for this issue: https://github.com/GrapesJS/grapesjs/pull/5176
artf
Thanks @krishnaeverestengineering but this is actually the expected behaviour for moving the component inside the same parent. This is because the at should account also for the index of the component itself. So, if you try to move "Compon...
krishnaeverestengineering
Thanks @krishnaeverestengineering but this is actually the expected behaviour for moving the component inside the same parent. This is because the at should account also for the index of the component itself. So, if you try to move "Compon...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome 114.0.5735.110 (Official Build) (64-bit)Reproducible demo link https://grapejs.com *EDIT: This site / domain serves malware, it is missing the "s" in the real grapesjs.com domainDescribe the bug Upon visiting grapejs....
tomsleeter
This is intermittent, I'm now getting grapejs.com homepage as expected
tomsleeter
Okay this was my mistake, I mis-typed the URL / domain name-- missing the "s" in grapesjs.com. Visiting URL grapejs.com is a bogus address with a bunch of malware / popups I believe the incorrect domain redirects to grapesjs.com every othe...
GJS Helper
It appears you've encountered a malicious website exploiting a common typo in the GrapesJS domain name. Thank you for reporting this critical observation. Root Cause and Explanation: The issue you've described is not a bug or vulnerability...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? AllReproducible demo link NoneDescribe the bug Following the documentation on creating a plugin with the usage of typescript and using the "usePlugin" function to import the plugin into the editor, the browser displays the f...
sneddobuilds
Getting the same issue.
GJS Helper
The TypeError: g.usePlugin is not a function error in GrapesJS typically arises from a misunderstanding of how plugins are registered and loaded, specifically confusing the global grapesjs library object with an editor instance. Root Cause...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Version 112.0.5615.49 (Official Build) (x86_64) Reproducible demo link https://jsfiddle.net/shomeelconovo/k7L2rthg/1/ Describe the bug I need help with something regarding the grapes.js. I have created a project and whenev...
The difference in default display properties between your GrapesJS project and the official demo stems from the CSS loaded within the GrapesJS canvas iframe, not from GrapesJS itself enforcing display: table or display: flex universally. G...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? ChromeReproducible demo link https://codepen.io/darrenbawag/pen/JjWBLrpDescribe the bug How to reproduce the bug?Open this link https://codepen.io/darrenbawag/pen/JjWBLrp and try to show the placeholder dropdown to toolbar o...
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...