GrapesJS Issues

3,464 parsed GitHub issues β€” 370 solved Β· 90 open. Search, filter and explore battle-tested answers.

743 issues found

πŸ” bug
#3526Jun 10, 2021by iabhiyaan1 answer
0 reactions

How to properly initialize grapesjs inside vuex store ?

This throws an error Maximum call stack size exceeded

GJSBlock

Thanks for reporting this, @iabhiyaan. The issue with Question: How to properly initialize grapesjs inside vuex store ? appears to be a race condition or state management timing problem. This typically happens when component lifecycle even...

#3511Jun 2, 2021by moises-flowize2 answers
0 reactions

Command core:component-enter not working in all the cases

WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grapesjs/blob/master/CONTRIBUTING.mdDo a quick SEARCH first, to see if someone else didn't open the same issueAll relative statements/questions have to be filled/answered, otherwise, th...

artf

Thanks @moises-flowize that will be fixed in the next release https://github.com/artf/grapesjs/commit/ac96298add119c4f4e000967ab3332f9ad711613

GJSBlock

Thanks for reporting this, @moises-flowize. The issue with Command core:component-enter not working in all the cases appears to be a race condition or state management timing problem. This typically happens when component lifecycle events...

#3497May 28, 2021by mosh-tudor2 answers
1 reactions

Button trait command doesn't work

Version: LatestDescribe the bug detailed https://jsfiddle.net/cleaver/wgz2jsvq/2/ Nothing happens on: --- On version 0.16.45 the same code worked fine: https://jsfiddle.net/cleaver/kenvpt50/1/

artf

Thanks for the report @tudor-ooo will be fixed in the next release

GJSBlock

Thanks for reporting this, @mosh-tudor. The issue with Button trait command doesn't work appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overla...

#3491May 27, 2021by TheDude702 answers
0 reactions

Iframe does not save src / does not recognize iframes after load

Version: 0.17.4 Are you able to reproduce the bug from the demo?[ ] Yes[X] No What is the expected behavior?After inserting an iFrame that the src will be returned when using editor.getHTML()When loading a page that iframes will be recognized as iframe component and become editable again Describe the bug detailed Am a...

artf

I'll add iframe support in the next release

GJSBlock

Thanks for reporting this, @TheDude70. The issue with iframe does not save src / does not recognize iframes after load appears to be a race condition or state management timing problem. This typically happens when component lifecycle event...

#3476May 24, 2021by krishnaeverestengineering3 answers
0 reactions

TypeError: Cannot read property 'querySelector' of null

<img width="1172" alt="Screenshot 2021-05-24 at 6 55 23 PM" src="https://user-images.githubusercontent.com/55732888/119354444-b8cbb500-bcc1-11eb-8e67-27e020c879aa.png"> I was getting this error while writing unit tests and I am testing editor instance to be defined. Randomly test case is passing but mostly I am gettin...

YyueeiWY

It seems like u are missing the class name or parent element ID. below is the example of using querySelector. <pre> var parentElement = document.getElementById('deviceready'); var listeningElement = parentElement.querySelector('.listening'...

artf

Sorry but this might depend on way too many factors (eg. your environment) and has nothing to do with the core itself.

GJSBlock

Thanks for reporting this, @krishnaeverestengineering. The issue with TypeError: Cannot read property 'querySelector' of null appears to be a race condition or state management timing problem. This typically happens when component lifecycl...

#3475May 24, 2021by ThetripGr2 answers
0 reactions

Toolbar/actionbar buttons do not work when there are multiple instances present (Even in your demo)

Version: 0.16.44 You can get the version by typing grapesjs.version into the console Are you able to reproduce the bug from the demo?[x] Yes[ ] No What is the expected behavior? Every instance has their own toolbar working properly Describe the bug detailed So previously i made another issue relating to instances #335...

artf

Thanks for the report @DodoTrip The fix is ready for the next release.

GJSBlock

Thanks for reporting this, @ThetripGr. The issue with Toolbar/actionbar buttons do not work when there are multiple instances present (Even in your demo) appears to be a race condition or state management timing problem. This typically hap...

#3472May 24, 2021by YyueeiWY2 answers
2 reactions

Css attribute (-webkit-background-clip:text;) doesn't work in grapesjs-preset-webpage.

Version: "grapesjs": "^0.17.3" "grapesjs-preset-webpage": "^0.1.11" You can get the version by typing grapesjs.version into the console Are you able to reproduce the bug from the demo?[x] Yes[ ] No What is the current behavior? Css attribute (-webkit-background-clip:text;) doesn't work in grapesjs-preset-webpage(disap...

YyueeiWY

Alright I solved it by using grapesjs-parser-postcss I didn't know there's a CSS parser plugin. https://github.com/artf/grapesjs-parser-postcss

GJSBlock

Thanks for reporting this, @YyueeiWY. The issue with Css attribute (-webkit-background-clip:text;) doesn't work in grapesjs-preset-webpage. appears to be a race condition or state management timing problem. This typically happens when comp...

#3470May 22, 2021by iabhiyaan1 answer
0 reactions

How can we active trait manager (of the top right panel) when component is selected

WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grapesjs/blob/master/CONTRIBUTING.mdDo a quick SEARCH first, to see if someone else didn't open the same issueAll relative statements/questions have to be filled/answered, otherwise, th...

GJSBlock

Thanks for reporting this, @iabhiyaan. The issue with Question: How can we active trait manager (of the top right panel) when component is selected appears to be a race condition or state management timing problem. This typically happens w...

#3465May 19, 2021by anatoli-dp3 answers
0 reactions

Update breaks some things with css

WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grapesjs/blob/master/CONTRIBUTING.mdDo a quick SEARCH first, to see if someone else didn't open the same issueAll relative statements/questions have to be filled/answered, otherwise, th...

artf

Well, actually the proper API would be .components('html string here') which seems to work as expected, but I'll investigate the reset thing because I'd expect to work the same way

artf

Ok seems like the backbone's reset method injects the silent option which prevents the CSS collection to render the added style, so for now, I'd prefer to avoid putting hacky conditions to remove that option and would recommend sticking wi...

GJSBlock

Thanks for reporting this, @anatoli-dp. The issue with update breaks some things with css appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overl...

#3463May 18, 2021by anatoli-dp4 answers
1 reactions

Inspector overflow broken

WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grapesjs/blob/master/CONTRIBUTING.mdDo a quick SEARCH first, to see if someone else didn't open the same issueAll relative statements/questions have to be filled/answered, otherwise, th...

anatoli-dp

Maybe put the controls in the front of the text and then offset the entire box slightly for each indent or stacked item. That way u can stack them as far as you want without issue 🀷 Im going to end up rolling my own solution to achieve th...

artf

Yeah, unfortunately, the default layer panel is not that scalable, we need to rethink how is rendered

artf

Yeah moving controls in front of the text sound reasonable (eg. and make them visible only when I hover the component). Anyway, being not such a common case having so much messy structure I wouldn't put a lot of priority on this problem, b...

Browse all topics