GrapesJS Issues

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

1180 issues found

#3578June 30, 2021by jcsofts1 answer
0 reactions

BUG: version 0.17.4 the components missing when try to add background image to body

I add domComponents: { storeWrapper: 1 }, when initialize the webeditor, to enable add background image to body. it works fine when use the local storageManager , but all the components lost when use the remote storageManager below is the data {"type":"wrapper","droppable":".container","attributes":{"id":"izmf"},"comp...

artf

Hi @jcsofts if the local storage works fine and your remote does not, that means you're probably doing something wrong on your endpoint side. I can't help you here without a reproducible example so I can only suggest following properly thi...

#3577June 29, 2021by alimajed932 answers
0 reactions

BUG: The UndoManager hasUndo() method returns true when it shouldnt

I am trying to disable the undo button when there are no undo actions to do. To do so, I am listening to 'change:changesCount' event, and using editor?.attributes?.UndoManager?.hasUndo() to set the undo button disabled state. editor.on('change:changesCount', editor => setHasUndo(editor?.attributes?.UndoManager?.hasUnd...

artf

So there is an extra action added to the queue while it shouldn't, which is when I am dragging a block over the canvas. Not really, are you able to create a reproducible demo, as I'm not able to reproduce it?

no-response[bot]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take ac...

#3573June 27, 2021by jasminder1 answer
0 reactions

BUG: Duplicate controls for every component

Version: 0.17.17 Are you able to reproduce the bug from the demo?[ ] Yes[x] No What is the expected behavior? It shouldn't show duplicate controls. What is the current behavior? Describe the bug detailed For some reasons, i am getting duplicate controls with vanila setup of gjs. Are you able to attach screenshots, scr...

artf

Add this to your init config in order to remove the default properties styleManager: { clearProperties: 1 },

#3564June 24, 2021by theSC0RP3 answers
0 reactions

BUG: Unable to refresh the iframe

0.17.19 Are you able to reproduce the bug from the demo? YES What is the expected behavior? I had asked a question regarding iframe refresh (#3413). The proposed solution was working for that version (0.17.3) and after running the piece of code the iframe should refresh and the canvas should be seen with the component...

artf

I would need to check why he is still trying to remove the frame, but for now, just skip this line frameView.remove()

theSC0RP

@artf. Thanks. This works when done once. If I do some action like a click inside the canvas and then if I run frameWrapView.render(); once again, I got another error. The screenshot and a video of this error are attached below. <hr> https...

artf

I'll try to fix it in the next release, but for now, you have to unselect components before frameWrapView.render() and reselect them back post rendering

#3559June 22, 2021by iabhiyaan2 answers
0 reactions

BUG: page.getMainComponent().view gives undefined when page is selected

Hello @artf, I want to get the HTML Element of selected page. But it returns undefined when using following code:

artf

Hi @iabhiyaan, when page:select triggers, iframes inside the canvas are not yet loaded, so you just need to wait once they are loaded before accessing its DOM.

iabhiyaan

Thankyou @artf.

#3549June 19, 2021by anlumoNo answers
0 reactions

BUG: createCustomEvent Doesn't Handle Mouse Events Correctly

Version: 0.17.4 / git master Describe the bug detailed FrameView repackages keyboard and mouse events here: https://github.com/artf/grapesjs/blob/07061ae1307fedf2a3b9bd585ce0cb30f653f112/src/canvas/view/FrameView.js#L389-L399 I think the reason is related to redirecting iframe events to parent frame events. This would...

#3548June 18, 2021by tannguyen971 answer
0 reactions

BUG: cann't copy with "control + C" when elements have attribute tabindex = -1

Hi everyone! i have a problem with custom component. i was created a modal component have attribute tabindex = -1 and i can't use key Ctrl + C to copy this component. Pls helps me. thanks very much !!!

artf

Just remove that attribute in your component view (eg. in onRender method) in that way you'll still get the attribute in your final HTML

#3547June 17, 2021by japo321 answer
1 reactions

BUG: Dragging multiple blocks reverses the order

Version: 0.17.4 Are you able to reproduce the bug from the demo? YES What is the expected behavior? When dragging the blocks, the order should be preserved. What is the current behavior? When dragging to the top or above the set of blocks, it goes in one order. When dragging to the bottom or below the set of blocks, i...

lexoyo

Hello I'm trying to fix this bug This is more of an exercise for me to dive in grapesjs code, let me know if I'm loosing my time or if it sounds useful

#3544June 15, 2021by maekawataiki1 answer
0 reactions

BUG: Trait Button Command not working on 0.17.4

Version:0.17.4 The trait with type button does not call command on 0.17.4 which is used to work before 0.17.3.Expected Behaviour Clicking button invoke command defined in trait.What is happening Clicking button does nothingjsfiddle example Command working on 0.17.3 -> https://jsfiddle.net/7pmz4u1v/3/ Command not worki...

mosh-tudor

@maekawataiki This is fixed, but not yet released - https://github.com/artf/grapesjs/issues/3497

#3534June 13, 2021by iabhiyaan3 answers
0 reactions

BUG: npm run build error

npm run build gives error @version 0.17.3../../lib/codemirror in ./src/editor/dist/grapes.min.js../css/css in ./src/editor/dist/grapes.min.js../javascript/javascript in ./src/editor/dist/grapes.min.js../xml/xml in ./src/editor/dist/grapes.min.js

artf

Give us more details about your build and the error

iabhiyaan

iabhiyaan

npm run build:css works fine. But npm run build gives those errors