GrapesJS Issues

Search parsed GitHub issues, see highlighted answers, and open the original discussion when needed.

1180 issues found

#4929February 14, 2023by handhikadj3 answers
0 reactions

BUG: a tag inside button is removed

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome LatestReproducible demo link https://codesandbox.io/s/interesting-bell-xntbtrDescribe the bug How to reproduce the bug?go to the codesandboxdrag and drop Custom Code block.put this code inside the Custom Code editor a...

artf

This happens because of the button implementation in the forms plugin, which allows only textnodes as children. If you remove the form plugin you'll be able to see the <a> element (if you prefer you can also extend the button component wit...

handhikadj

so what is the code of "normal" implementation of the button? btw, may I know why do you make the button to behave like that on the forms plugin?

artf

If I recall properly the main reason there was a problem with inline text editing with button elements, so that approach was the easiest way to fix a common issue. I guess the "normal" implementation would be to skip/overwrite the init met...

#4922February 11, 2023by clonefunnels1 answer
0 reactions

BUG: Using !important code provided here breaks background image and gradient.

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefox Reproducible demo link https://jsfiddle.net/jLgb0mv3/1/ Describe the bug How to reproduce the bug?...Put this code in the editor: editor.on('styleable:change', (model, property) => { const value = model.getStyle()[...

artf

I only see the issue with composite/stack style manager properties and that is because not every style manager property is part of the styles so in your code you would only need to check if the value of the style actually exists, eg. if (v...

#4921February 8, 2023by ghost2 answers
0 reactions

BUG:

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Version 110.0.5481.78 (Official Build) (64-bit) Reproducible demo link https://grapesjs.com/demo.html Describe the bug How to reproduce the bug?Install GrapesJs with npm or CDN and initialize as usual to a container...

artf

Closing as this is not related to the core but to the demo page, please make a PR if you want to suppress those warnings

ghost

this is related to core not demo page , since i used the demo page for illustration

#4920February 8, 2023by c9a23341 answer
0 reactions

BUG: Missed localization keys for de locale

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Not browser related Reproducible demo link https://codesandbox.io/s/pensive-river-417grm?file=/index.js Describe the bug How to reproduce the bug?import grapesjs/src/i18n/locale/de.jsuse this as a locale in your editor con...

artf

Thanks @c9a2334 would you like to contribute on this fix?

#4919February 8, 2023by maliuta-oleksandr1 answer
0 reactions

BUG: calling destroy method breaks the editor ( React app )

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 109.0.5414.119 Reproducible demo link Describe the bug How to reproduce the bug?add event listener to outside clickcall destroy method What is the expected behavior?Destroying without errors What is the current beha...

artf

Are you able to provide a reproducible demo as I'm not able to reproduce it on my end?

#4912February 6, 2023by lexoyo2 answers
1 reactions

BUG: broken links in the docs

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? any Reproducible demo link no Describe the bug Since the move from artf to GrapesJS I believe many links are still to the original repo https://github.com/GrapesJS/grapesjs/search?q=artf Should I try to replace it or do we...

lexoyo

I did a PR, I hope I didn't miss anything, I had to test almost each link

artf

I think some stuff are redirecting but others might be broken, I'd appreciate a PR if anyone is willing to help 🙏

#4906February 6, 2023by panditlakshya1 answer
0 reactions

BUG: Grapesjs fails to recognize component types when setting innerHTML through script.

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? chrome v108.0.5359.98 Reproducible demo link https://codesandbox.io/s/grapes-js-template-literal-forked-6kgvrb?file=/src/App.js Describe the bug I'm trying to create a custom component that recognizes inner html component...

artf

Read carefully this guide, everything inside script is outside of the editor scope. You can update the component itself by using component.components method or specify the components: '<div ....' directly in definition.

#4904February 5, 2023by handhikadj1 answer
0 reactions

BUG: getHtml() producing invalid structure when there is js inside it

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? chrome latestReproducible demo link https://jsfiddle.net/snj87o6f/1/Describe the bug Context/Description I think this is a bug because I need to save and load the data back with editor.Parser.parseHtml on onStore of storageM...

artf

The output is correct (check the real console not the broken one from jsfiddle) and read carefully this section, you should never rely on HTML/CSS to load back the project.

#4900February 5, 2023by handhikadj1 answer
0 reactions

BUG: setStyle/getCss() produces duplicated css

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome LatestReproducible demo link https://codesandbox.io/s/silent-river-ifczcvDescribe the bug How to reproduce the bug?Visit the siteSee console. Pay attention to the * and body selector Expected result Should not be dupl...

artf

There are default styles applied that you can simply disable (pass an empty string) https://github.com/GrapesJS/grapesjs/blob/a83847b1b35e69e5a5810ccf1eb1e1384bf0aab1/src/editor/config/config.ts#L143-L147

#4897February 3, 2023by rudacs3 answers
1 reactions

BUG: component:styleUpdate / component:styleUpdate:propertyName not fired

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Edge 109.0.1518.70 Reproducible demo link https://jsfiddle.net/rudacs/kr2x1mnh/ Describe the bug How to reproduce the bug?Change some property in StyleManager.Change the width property on the StyleManager. What is the expe...

artf

Hey @rudacs did you try instead using style:property:update?

rudacs

This event worked. Was it changed to this one? And for a single property? How do I get what was the component and property changed? Tranks.

SagarMaria

came here because I have the same issue. Using the suggested style:property:update seems to work, but for some reason it fires on every click. Also, how can we target a particular style property change, i.e. text-align?