GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Opera 10.0.5130.23 | Linux Reproducible demo link https://grapesjs.com/demo.html Describe the bug Clear canvasFrom Blocks menu add 1 Column component -> Settings tab is opened automatically :ok_hand: Click newly added comp...
artf
Thanks @gladykov but this is not related to the core, it's just an example behavior implemented in the demo.
GJS Helper
This is a valid observation regarding user experience in GrapesJS. The behavior you're describing is not a bug in the sense of a broken feature, but rather a UX inconsistency where clicking an already selected component doesn't always re-a...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? FIrefox Reproducible demo link https://grapesjs.com/docs/modules/Assets.html#initialization Describe the bug How to reproduce the bug?Go to https://grapesjs.com/docs/modules/Assets.html#initializationClink to the below lin...
GJS Helper
Thank you for reporting this issue. You've correctly identified a broken link in the GrapesJS documentation for the Asset Manager. Root Cause: The link provided in the documentation for AssetImage.ts incorrectly points to the dev branch of...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefoxe 125.0.3 (64 bits) Reproducible demo link https://grapesjs.com/demo-newsletter-editor.html Describe the bug How to reproduce the bug?install latest version of grapejsclick on fullscreen select a text or block with...
vincepv
Issue solved. I find a solution. When I init grapejs, I pass object config with colorPicker const config = { container: '#editor', fromElement: true, // other config options here colorPicker: { appendTo: 'parent', offset: { top: 26, left:...
artf
Thank @vincepv yeah there might be some conflicts with the fullscreen command and the default configuration of the color picker depending on how and where the editor container is rendered. Probably, in most of cases, it would be enough to...
GJS Helper
The issue you're encountering, where the color picker is hidden when GrapesJS is in fullscreen mode, is a common problem related to stacking contexts and how fullscreen elements are rendered. It's not a bug in the color picker itself, but...
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? 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? 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? 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...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? N/AReproducible demo link https://grapesjs.com/demo.htmlDescribe the bug Hi everyone !!! <3 How to reproduce the bug?open grapesjs official webpage democlick on a container, e.g. the hero section containerapply a font-weight...
artf
i need to select something else then normal again Yeah in case there are no values, the default UI preselects the default value, but that can be easily updated So I guess this is not a core bug but an "unexpectedly expected" behavior π₯²
lexoyo
Oh ok, I thought you would want the default default value to be the expected expected behaviour π Thank you for the answer
GJS Helper
Hi there! Thanks for reporting this issue. You've accurately identified a common point of confusion and a valid usability concern within the GrapesJS Style Manager regarding default CSS property values, especially when dealing with inherit...