GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link https://jsfiddle.net/szLp8h4n Describe the bug How to reproduce the bug?Create a blockClick itGo to the traits tabSet an new IDGo to the styles tabSee the ID hasn't changed (under class) To se...
GJS Helper
This is indeed a known synchronization issue within GrapesJS where the Styles tab's selector display doesn't immediately reflect changes made to a component's ID via the Traits panel. The behavior you described is accurate and reproducible...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? ChromeReproducible demo link testDescribe the bug I don't see any way to show icons or shapesCode of Conduct[X] I agree to follow this project's Code of Conduct
artf
Please use the Discussions panel if you have questions.
GJS Helper
GrapesJS, being a highly flexible and unopinionated framework, doesn't include a built-in set of icons or shapes by default. Instead, it provides powerful APIs to integrate any external library or create custom components to achieve this....
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v121Reproducible demo link https://jsfiddle.net/L27powtg/30/ (the fix it also there, commented out)Describe the bug How to reproduce the bug?Create a custom GJS component for template tags as explained here: https://g...
GJS Helper
This is indeed a known behavior when dealing with HTML fragments that are not valid in a standalone context, such as <tr> or <td> tags outside of a <table> element. GrapesJS, like many HTML parsers, relies on browser-native DOM parsing mec...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Version 123.0.6312.123Reproducible demo link Uncaught TypeError: _webpackrequire_.r is not a function at ./nodemodules/grapesjs/dist/grapes.mjs (grapes.mjs:1:1) at _webpackrequire (bootstrap:789:1) at fn (bootstrap:150:1) at...
Mustufask
@artf pls help me solve this issue as this node modules files doesnt allows grapesjs to work in my react based project
artf
Related discussion https://github.com/GrapesJS/grapesjs/discussions/5400 Please use the search before opening an issue.
GJS Helper
The Uncaught TypeError: _webpackrequire.r is not a function error you're encountering is a common Webpack-specific issue related to how it handles ES Modules (files ending in .mjs) and its internal module interop logic. The webpackrequire....
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 123.0.6312.123 Reproducible demo link https://jsfiddle.net/35Lq26du/1/ Describe the bug How to reproduce the bug? 1.Insert any container,column etcChange background color of any one of the group,If you inserted two...
GJS Helper
The issue you're encountering where changing the background color of one container affects others is not a bug in GrapesJS's core functionality, but rather a direct consequence of how CSS works in conjunction with GrapesJS's fromElement: t...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v123Reproducible demo link https://jsfiddle.net/xwgons8z/Describe the bug I'm trying to programmatically move an added component to a specific position in the parent since I have child components, that are supposed to...
rhoenerSBS
I initially wanted to realize the same behavior with a function in the droppable property of the parent component to prevent components being dropped at a specific index but unfortunately the index is not given as a param for that function.
GJS Helper
Thank you for reporting this issue. You've identified a subtle timing bug in GrapesJS related to how the Layers panel updates when a component is programmatically moved immediately after being added. Root Cause The issue stems from a timin...
Reproducible demo link https://node-projects.github.io/web-component-designer-demo/index.htmlDescribe the bug I started a Framework to design webpages with webcomponents a few years ago, and now I found GrapeJS. Thought maybe we have the same goals and could benefit from each other? (Don't know how atm., but maybe) (l...
GJS Helper
Thank you for reaching out and for your interest in GrapesJS! It's great to see other innovative projects in the web design space. Your Web Component Designer looks very interesting, especially with its strong focus on web components, adva...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Arc Version 1.35.0 / Chromium Engine 123.0Reproducible demo link https://grapesjs.com/demo.htmlDescribe the bug My special case: In my case, all styles from plugins and general styles are located in the header. So, to achiev...
artf
it is intended to store canvas styles, styles that do not affect the result of hmtl/css, styles that will not be exported, right? Correctby default the body has a white background, this seems to be the default color in all browsers, no? ye...
artf
There is canvasCss option for that. Next time open a Discussion please, as this is not a core bug but wrong usage.
ctrhub
Hey @artf. Thanks for the answer. I'm not sure that we understood each other and I would like to clarify one detail. Yes, I know about the canvasCss property, moreover, I use it to change the styles of the selected component. I understand...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v123 Reproducible demo link https://jsfiddle.net/7xu0efLc/3/ Describe the bug The GrapesJs docs show that it is supposedly possible to filter the blocks and rerender the BlockManager with the filtered list of blocks...
artf
That method is only valid once the default block manager is already rendered. If you need to rerender at the beginning you can subscribe to the event of block manager activation.
rhoenerSBS
Thank you @artf
GJS Helper
The issue you're encountering with BlockManager.render() not filtering blocks as expected stems from a common misunderstanding of how GrapesJS (and its underlying Backbone.js framework) handles collections. While the documentation states t...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefox Reproducible demo link dist/index.d.ts Describe the bug Typping error ?proeperty instead of property don't know if it's serious lines 8053/8054 : addBuiltIn(prop: string, definition: Omit<PropertyProps, "property">...
GJS Helper
Thank you for reporting this typographical error in the GrapesJS TypeScript declaration file. You are absolutely correct; there is a typo on lines 8053/8054 of dist/index.d.ts. Root Cause The issue is a simple typo where proeperty is used...