GrapesJS Issues

ahmedderkaoui

try to work with vh instead of px. eg: give the editor height: '80vh', your navbar height: '20vh'. This way, the vertical scroll will never be shown or needed as long as the sum of all elements's vh ≤ 100 Hope this helps.

samichamoun

try to work with vh instead of px.eg: give the editor height: '80vh', your navbar height: '20vh'. This way, the vertical scroll will never be shown or needed as long as the sum of all elements's vh ≤ 100Hope this helps. thanks this is usef...

artf

This is more a layout issue and not related to the GrapesJS editor itself.

artf

Follow the issue template

GJSBlock

Thanks for reporting this, @ahmedderkaoui. Thanks for sharing your report about setMessages() does not update i18n. To help the team investigate and prioritize this: Please provide: A minimal reproducible example (CodeSandbox/JSFiddle) You...

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...

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...

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...

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...

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...

iabhiyaan

`

artf

mmm what is the point? Your custom traits should already react to component changes (if you created them properly).

GJSBlock

Thanks for reporting this, @ahmedderkaoui. Great question about Refresh/Re-render traits of all components in canvas. The recommended approach with Canvas is to use the event-driven API. Start here: Check the GrapesJS documentation for you...

GJSBlock

Thanks for reporting this, @ahmedderkaoui. Great question about Re-render trait on selected component. The recommended approach with Components is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific...

artf

Please follow the issue template

GJSBlock

Thanks for reporting this, @Redix0. Security and dependency issues are important. The GrapesJS team actively works on keeping dependencies up-to-date. For you right now: Run npm audit fix to see available patches Check for a newer GrapesJS...