GrapesJS Issues

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

1180 issues found

#1914March 22, 2019by lyczos2 answers
0 reactions

[Bug] Change default font size unit to EM instead of REM.

Now in GrapesJS editor, we have some of font sizes in REM. I think they should be in EM unit because if we want to embed editor in the existing page there may be some issues with proper font size - in case when the parent font size is set to other then default size (ex. :root { font-size: 10px }). https://i.imgur.com/...

artf

Yeah, I think you're right, would you like to create a PR?

lyczos

Yep, sure, I will do it later :)

#1913March 21, 2019by SylvainBigonneau3 answers
2 reactions

[BUG] Specifying background-size in background's properties breaks grapesjs

Using latest versions of grapesjs (0.14.55) and grapesjs-preset-webpage (0.1.10), I have configured my editor as such: The library crashes with a "TypeError: values[0] is undefined" error, as referenced in this issue. If I add all the other properties in the array, such as: the error disappears, but I don't need all o...

artf

Ok, I think I found where is the issue, I'll fix it for the next release

SylvainBigonneau

Can confirm it's fixed on v0.14.57. Thanks @artf !

lock[bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

#1907March 19, 2019by u-ashikov2 answers
0 reactions

[QUESTION]: Drag and drop external html to editor ?

I have created a component which is heading and a block element for it. I have set the draggable property to be section html element. If I try to drag and drop external heading html element to the editor, it is dropped, but if I try to drag and drop the heading block element (which I have defined in the editor), it is...

artf

I have set the draggable property to be section html element. it is not allowed to drop if it is outside the section. Should it work this way, or it is a bug ? Well, if you set draggable: 'section' it means you can drag that heading compon...

lock[bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

#1903March 19, 2019by MisterFK2 answers
0 reactions

[BUG] map block issue

Hi, There is a "404" issue when drag&drop a map into canvas since the last release. The problem is also in your demo. Do you know how to fix that plz? Thanks for help !

artf

For now, add this I'll fix it the next release

lock[bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

#1900March 17, 2019by cgrio2 answers
0 reactions

bug - plus sign ("+") not show if change the selection

to simulate de bug follow the steps: Click on a element in canvas Click on tab to add class click on the plus sign to add new class string click in other elements in canvas click on tab to add class "The button + is hidden" Suggestion reset the behavior of class + button everytime that some element is selected in canv...

cgrio

its a problem with css

lock[bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

#1898March 16, 2019by foolsopts2 answers
0 reactions

some bug in grapedrop

Step to producedrag image-block to canvas and select background.drag icon to canvas.click on image-block and go to background style tab click on background and click image button.when modal shown click on any image (not double click) then close modal.Now look at the icon in canvas you cannot change it to another icon....

artf

You're right, weird issue, I'll check it later. I'm gonna close it as is part of the Grapedrop product and not the grapesjs core, btw thanks for the report

lock[bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

#1896March 16, 2019by kaoz703 answers
2 reactions

[BUG] Component from custom plugin is not recognized

OS: Windows 10 x64 Browser: Chrome 72.0.3626.121 x64 GrapesJS: v0.14.55 Hello, I have some custom components (bootstrap tabs) in a plugin, for some reason some of the components of the plugin are not being detected by GrapesJS when loading it from the container elements, and others via dragging and dropping into the e...

artf

As you see, its type is div... this is why it never reaches the other type... look why and where that type is declared

kaoz70

Alright, that was the issue! I thought that the 'div' type was a default one set by GrapesJS. Thanks for all the help!

artf

It might be that elHasClass method?!?

#1895March 15, 2019by simplecommerce3 answers
0 reactions

[QUESTION] Drag component over canvas with script, script appended multiple times.

Hi, not sure if this is a bug or not. But I noticed a weird behavior, when I drag a block that has a component that contains a script function, it seems to append it into the canvas before its being dropped. And as you drop it, it appends another time, the script. If you never drop the block and just drag over and out...

simplecommerce

So I dug around and figured that it was the updateScript method in the canvasView that was being called every time a script property is found on a component, regardless if its still being dragged or not over the canvas. I did some patching...

simplecommerce

My previous solution did not work, so I had to scrap it, so I re-opened the issue.

artf

Hi @simplecommerce if you think it's a bug, please open an issue by FOLLOWING the template and create a reproducible live demo of the issue. It's really important because as we don't have a lot of free time we risk to waste a big part of i...

#1894March 14, 2019by jwilson-lyonscg2 answers
0 reactions

[BUG] Custom Trait documentation example doesn't work

Specifically this: https://grapesjs.com/docs/modules/Traits.html#define-new-trait-type First of all, the keyUp event references onChange when the function name is actually onChange. Next, even if you fix this, this.model.get('value') evaluates to a blank/null value whenever I make changes to it. The only way I can see...

jwilson-lyonscg

Nevermind. I was misunderstanding the syntax. I didn't realize that the onChange and the onValueChange are 2 different unrelated methods apparently. It's not clear to me what onChange does exactly.

lock[bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

#1891March 14, 2019by jwilson-lyonscg3 answers
0 reactions

Can't create new button component

I'm having a hard time creating a new component for a <button> element. What am I missing? Is something bugged out here? Works fine if I change it to an <input> element:

jwilson-lyonscg

Okay so after some more experimentation it appears my component structure is correct, but my button block was not working correctly. So the button block was like this: When dragging this block into the canvas, this did not get recognized a...

artf

I think the problem here is a misunderstanding of content key. When you declare a block The content is for the Component, like a string o like an object. The string version of the example above would be: But when you use content inside a C...

lock[bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.