GrapesJS Issues

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

1180 issues found

#4837January 10, 2023by quentin-bettoum3 answers
4 reactions

BUG: HTML elements ids are incremented on different pages loaded in projectData

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefox 109 Reproducible demo link https://grapesjs.com/demo.html Describe the bug Hello, I noticed that when I load multiple pages in the projectData that have the same id used in the HTML, grapes will automatically incre...

artf

hey @bgrand-ch I think one day all grapesjs entities will have a global uid, so in long-term, I'd expect this issue to be fixed 🤞

quentin-bettoum

At first, I wanted to generate all the pages together to have a single CSS output for all the pages. But now I'm trying another solution for the styles. So for the id problem, generating each page separately could be a solution. Thanks for...

bgrand-ch

Grapes to use some data attributes (something like data-grapes-id) as unique identifiers to leave the id free for some frontend scripts. I like this idea 💯

#4817January 2, 2023by sdimitrenco1 answer
0 reactions

BUG: Can't edit text node inside div, if div has inside tag p > span.

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome Version 108.0.5359.125, Mozilla 107.0Reproducible demo link https://jsfiddle.net/stanislavdimitrenko/d61cm4yg/14/Describe the bug So, that strange behavior of grapes js. If you have that struct "Some text without the...

artf

Yeah right now this is an expected behaviour for parsed text nodes without proper wrappers and not textable components as siblings. So in order to make those nodes editable you have to properly wrap them in a tag like span.

#4812December 27, 2022by FaisalShaikhHA1 answer
1 reactions

BUG: Layerable property not working as expected in parent-child scenario.

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? 107.0.5304.110 (Official Build) (arm64) Reproducible demo link https://codepen.io/faisal-praella/pen/rNvOwgR Describe the bug When the parent component is set to layerable: false it is not visible & all its child not visib...

artf

Unfortunately this is how layerable currently works so it's not a bug, but I'd be glad to accept a PR to improve this behaviour.

#4803December 25, 2022by miladmeidanshahiNo answers
0 reactions

BUG: Traits value type select doesn't fill value

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 108 Reproducible demo link https://grapesjs.com/demo.html Describe the bug How to reproduce the bug? Use the tooltip component and get Traits via editor.getSelected().getTraits() as you can see data-tooltip-length v...

#4801December 23, 2022by eduardocalixtokorp1 answer
1 reactions

BUG: React components componentWillUnmount is not called

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome 108.0.5359.125 (Windows)Reproducible demo link https://codesandbox.io/s/white-meadow-o56l2d?file=/src/Chart/Chart.js:135-254 This demo is not in the latest grapesjs version, but locally, using the latest version, I ha...

eduardocalixtokorp

I've noticed that in my component definition I was doing reactRoot.render(<>{reactEl} </>) in onRender() then, I was missing to add root.unmount() n remove() method

#4800December 23, 2022by usmanqamar-int1 answer
0 reactions

BUG: Removing or adding component changes other components locations with dragMode translate, any solution please?

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link https://zmzr3n.csb.app/ Describe the bug How to reproduce the bug? While deleting or adding more than one component, other components have changed their position. What is the expected behavior...

artf

This is how translate works, the alternative is to use absolute mode

#4799December 23, 2022by AgnRakul1 answer
0 reactions

BUG: Issues on setDragMode in version 0.20.2

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link https://jsfiddle.net/6c7xw3Lu/2/ Describe the bug Screencast from 23-12-22 12:24:15 PM IST.webm DragMode Issues on Version 0.20.2 The Dragging visually is not viewed on video kindly check once...

artf

This is related to this issue and it's ready for the next release.

#4797December 21, 2022by vaneatkaNo answers
0 reactions

BUG: change type keepUnusedStyles?: 0;

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? any Reproducible demo link n/a Describe the bug Please fix the type for keepUnusedStyles?: 0; https://github.com/artf/grapesjs/blob/dev/index.d.ts#L261 to avoid code like this keepUnusedStyles: true as any, thank you.Code...

#4792December 19, 2022by wunksert3 answers
0 reactions

BUG: Drag and drop broken in 20.2

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v108Reproducible demo link see belowDescribe the bug How to reproduce the bug?Create a custom componentAdd it to the editor as a component and draggable blockSet the editor to absolute drag mode when the component add...

wunksert

Confirmed it's still working in v0.20.1, so it looks like the regression was introduced in v0.20.2

wunksert

The component is no longer draggable once it's added to the canvas either.

artf

I'll prepare a fix for the next release.

#4791December 19, 2022by joukhar1 answer
0 reactions

BUG: block:drag event not working in touch devices even after including touch plugin

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? chrome desktop Version 108.0.5359.125 latest Reproducible demo link N/A Describe the bug How to reproduce the bug? when dragging component from block manager, the event is not fired. If is necessary to execute some code in...

artf

Thanks @joukhar there is actually some inconsistency with the block:drag event and I'll try to fix it in the next release.