GrapesJS Issues

3,464 parsed GitHub issues โ€” 370 solved ยท 90 open. Search, filter and explore battle-tested answers.

545 issues found

๐Ÿ” typescript
#5785Mar 29, 2024by bernesto3 answers
1 reactions

Outlines persist in preview mode

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 This may be by design, but it seems odd given the intent. How to reproduce the bug?Click preview (eye) What is the expected behavior? The p...

bernesto

Awesome @artf you are a rockstar!

artf

Thanks @bernesto there is actually an update to do on the demo side. I prepared the change and will fix it on the next release.

GJS Helper

You've identified a common point of confusion regarding GrapesJS's preview mode. The behavior you're observing, where component outlines (dashed borders) persist in preview mode, is indeed not the intended user experience for a clean, end-...

#5775Mar 26, 2024by ctrhub2 answers
0 reactions

Component.get('traits').clone() is no longer available.

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Arc Version 1.35.0 / Chromium Engine 123.0 Reproducible demo link https://grapesjs.com/demo.html Describe the bug How to reproduce the bug?Open dev toolsSelect a componentRun in console: What is the expected behavior? Shou...

artf

If you need to make a copy of traits I'd suggest simply doing this JSON.parse(JSON.stringify(editor.getSelected().getTraits())). I don't remember ever mentioning cloning traits in docs, so I'd avoid using non-public APIs.

GJS Helper

You've identified a legitimate bug in GrapesJS where calling component.get('traits').clone() throws a TypeError. This issue arises because the Traits collection's clone() method, which internally relies on Backbone.Collection.prototype.clo...

#5768Mar 19, 2024by rhoenerSBS1 answer
0 reactions

Wrong Type for "content" property in BlockProperties

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 GrapeJs Docs indicate that it is possible to add mixed content to the "content" property of a block (see https://grapesjs.com/docs/modules/Blocks.html#...

GJS Helper

You've accurately identified a discrepancy between the GrapesJS documentation and its TypeScript type definitions for the content property within BlockProperties. This is indeed a bug in the type definition, as the content property is desi...

#5739Mar 11, 2024by rhoenerSBS1 answer
0 reactions

Wrong Type in ColorPickerOptions Interface

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...

#5729Mar 8, 2024by Sphenox4 answers
1 reactions

Editing/replacing the text inside of a link

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.

#5724Mar 8, 2024by bernesto2 answers
0 reactions

Whitespace handling in inline elements

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...

#5720Mar 6, 2024by bernesto2 answers
0 reactions

Propagating component defaults can break layers when child comments are introduced

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...

#5715Mar 4, 2024by afrinxnahar1 answer
0 reactions

Broken link in the API docs

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...

#5703Feb 25, 2024by bernesto1 answer
0 reactions

Color picker offset relative to editor container

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...

#5700Feb 24, 2024by upadhyay88442 answers
0 reactions

=

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...

Browse all topics