GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122 Reproducible demo link not applicable Describe the bug The ColorPicker Interface that came with the latest release, defines the "preferredFormat" option to expect a 'boolean' value but the docs of the Spectrum...
GJS Helper
This is indeed a valid bug report regarding the TypeScript type definitions in GrapesJS for the ColorPickerOptions interface. The preferredFormat property is incorrectly typed as boolean when it should be string according to the underlying...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122 Reproducible demo link https://grapesjs.com/demo.html Describe the bug How to reproduce the bug?Open demoCreate a text, with a link in it edit text with the default RTEselect the whole linktype anything, to rep...
bernesto
@artf, you're right again. Whitespace in the node matters. If the text butts right up to the closing node, the first keystroke replaces the text, the next keystroke exits the node, if not, it works as one would expect. There is an old thre...
bernesto
Just to clarify, you are referring to the selection of and editing of the text within the link behaving abnormally like this?
Sphenox
Yeah, excactly as shown in the video you provided.
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v122Reproducible demo link https://jsfiddle.net/zwo0mdqf/5/Describe the bug How to reproduce the bug?Create valid inline block elements such as span, b, i, em, etc. that use multiple space, tab(s), or line breaks as w...
danstarns
Closing in favor of merged commit. https://github.com/GrapesJS/grapesjs/pull/5719
GJS Helper
The issue you're encountering with whitespace handling in GrapesJS, specifically with inline elements and the getHtml() output, stems from how HTML parsers and GrapesJS's component model treat different types of whitespace. Root Cause HTML...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122 Reproducible demo link https://jsfiddle.net/n38vbktg/ Describe the bug How to reproduce the bug?Create a component that propagates defaults that include layerable = true. Introduce a comment under the competent...
artf
Good catch @bernesto
GJS Helper
This is a valid bug report. The issue arises because GrapesJS's component system, particularly when layerable: true is propagated, attempts to process HTML comment nodes as if they were standard HTML elements. This leads to errors when met...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Version 122.0.6261.95 (Official Build) (64-bit) Reproducible demo link https://jsfiddle.net/n4x6L1v0/2/ Describe the bug How to reproduce the bug?Save component data from an earlier version of grapejs (0.18)Attempt...
artf
Thanks @mitcht but as I already mentioned the main component could never been textnode in the first place so it doesn't make sense to handle such a case in the core or have this issue open. Anyway, if the logic works for you just use it in...
GJS Helper
The issue you're encountering is a known breaking change related to the evolution of GrapesJS's internal component architecture, specifically how the root component of a frame is handled. In older versions (like 0.18), the default root com...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefox Version 123.0 (64-bit) Reproducible demo link Not present Describe the bug I guess most of the .js files have been turned into typescript but there might be more broken links like the below one.. Code of Conduct [X...
GJS Helper
Thank you for reporting this broken link in the GrapesJS API documentation. You've correctly identified the root cause. Root Cause The GrapesJS project has been undergoing a significant migration from JavaScript to TypeScript. As part of t...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? chrome latest Reproducible demo link we are running on local machine now Describe the bug Hello, right now grapesjs provides built in properties like margin, padding that allow user to change each property one by one (marg...
artf
Please avoid opening BUG issues without reading the actual point of bug issues in the template.
GJS Helper
It's a great suggestion to enhance the GrapesJS styling experience! By default, GrapesJS's Style Manager provides granular control over CSS properties like margin and padding, allowing you to adjust each side (top, right, bottom, left) ind...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122 Reproducible demo link https://jsfiddle.net/Lk2bwhp4/ Describe the bug How to reproduce the bug?Place the editor inside of a container, then programmatically resize the container's width. What is the expected b...
artf
Thanks @bernesto for the report but as we can't detect programmatic layout changes without impacting the performances, in this case, you have to update the editor layout manually via editor.refresh() (eg. in your example you would put the...
bernesto
Hi @artf, I actually had this accidentally mixed in the last pull request you accepted (src/canvas/model/Frame.ts). You might want to take a look at what I added and see if it is causing an issue. We have it in testing right now and haven'...
artf
I actually had this accidentally mixed in the last pull request you accepted and I actually removed it cause it seemed to be unrelated ๐คฃ Not a problem to add it back but consider that your example will work only because of the desktop Dev...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122 Reproducible demo link https://jsfiddle.net/v4e5d90z/ Describe the bug How to reproduce the bug?Place the editor in any container. What is the expected behavior? The color picker should appear relative to the i...
GJS Helper
The issue you're experiencing with the GrapesJS color picker appearing offset is a common problem related to how third-party popup components (like color pickers, tooltips, or dropdowns) handle their positioning, especially when the main a...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? chromeReproducible demo link Cannot provide it data is sensitiveDescribe the bug How to reproduce the bug?Drop a page in the editor/Canvas.Set height for ex- 600pt and also give padding of 10 pt to all 4 sides.Now drop two s...
upadhyay8844
@artf can you please have a look at it ?
GJS Helper
The issue you're encountering, where a child section with height: 100% overlaps its parent when the parent has fixed height and padding, and other siblings are present, is a common CSS layout challenge. It's not a bug in GrapesJS itself, b...