GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v128 Reproducible demo link https://app.grapesjs.com/studio Describe the bug After adding a Page, removing it with undo and adding back with redo, the page is not working properly. The Layer Manager does not update...
artf
Thanks for the report @rhoenerSBS
GJS Helper
This is indeed a bug in GrapesJS's undo/redo mechanism, specifically when handling page additions and removals. The behavior you've described is consistent with an incomplete restoration of the page's internal state after a 'redo' operatio...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome 91VReproducible demo link https://jsfiddle.net/8tsj5vpb/Describe the bug I'm encountering an issue with GrapesJS where traits defined for a custom component are not being displayed after reloading the editor. The trai...
mohamedsalem401
@Alababdiy I was unable to reproduce the issue using the link provided. However, it seems like the issue is that GrapesJS doesn't allow adding or defining a component after it has been initialized.
mohamedsalem401
Hey @Alababdiy, I wasn't able to reproduce the issue you described in the JSFiddle.
GJS Helper
You've encountered a common issue related to how GrapesJS persists and re-identifies custom components after reloading the editor. The traits for your custom component disappear because GrapesJS is not correctly re-associating the loaded c...
The process for publishing the build artifacts of the GrapesJS repository has had the following issues: Artifacts are expected to come directly from developers' machines. - https://github.com/GrapesJS/grapesjs/pull/6041 The process is undocumented We have multiple packages to release, and proper documentation is also...
GJS Helper
The issues regarding the GrapesJS release process โ specifically, the reliance on developer machines for artifacts and the lack of documentation โ highlight a need for a standardized, automated, and transparent workflow. Adopting an indust...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link https://codepen.io/Harshsne/pen/xxoOyXO Describe the bug https://github.com/GrapesJS/grapesjs/issues/6019 with reference to this, I wanted to hide rte only for some particular type . Example:...
The issue describes a common need to conditionally control the Rich Text Editor (RTE) in GrapesJS, specifically preventing it from activating for certain component types, such as 'link' components. While GrapesJS automatically enables RTE...
GrapesJS version[x] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome 126.0.6478.127Reproducible demo link https://jsfiddle.net/6m53pwy7/4/Describe the bug How to reproduce the bug? I'm looking to use Tailwind with GrapesJS, but this framework uses Utility-First CSS Classes to build qui...
artf
You need to escape properly the CSS
GJS Helper
It appears you've encountered a known limitation or bug in GrapesJS's CSS parsing and style management when dealing with selectors that contain escaped colons (\:), which are common in frameworks like Tailwind CSS for responsive variants (...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? FIrefox Reproducible demo link https://grapesjs.com/docs/modules/Assets.html#initialization Describe the bug How to reproduce the bug?Go to https://grapesjs.com/docs/modules/Assets.html#initializationClink to the below lin...
GJS Helper
Thank you for reporting this issue. You've correctly identified a broken link in the GrapesJS documentation for the Asset Manager. Root Cause: The link provided in the documentation for AssetImage.ts incorrectly points to the dev branch of...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefox 125.0.3, Brave 1.66.110 Reproducible demo link https://jsfiddle.net/szLp8h4n Describe the bug Following the 'git' instructions to install Grapesjs when you execute 'yarn start' in Terminal: ~$ sudo apt install node...
artf
Thanks @shapley yeah it's not really related to GrapesJS or even yarn, you have to increase file system watchers
GJS Helper
The ENOSPC: System limit for number of file watchers reached error you're encountering is a common issue on Linux systems, including Ubuntu 24.04 LTS, when working with large projects that have many files, such as the GrapesJS repository w...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v123 Reproducible demo link https://jsfiddle.net/7xu0efLc/3/ Describe the bug The GrapesJs docs show that it is supposedly possible to filter the blocks and rerender the BlockManager with the filtered list of blocks...
artf
That method is only valid once the default block manager is already rendered. If you need to rerender at the beginning you can subscribe to the event of block manager activation.
rhoenerSBS
Thank you @artf
GJS Helper
The issue you're encountering with BlockManager.render() not filtering blocks as expected stems from a common misunderstanding of how GrapesJS (and its underlying Backbone.js framework) handles collections. While the documentation states t...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122 Reproducible demo link not applicable Describe the bug The GrapeJs Docs indicate that it is possible to add mixed content to the "content" property of a block (see https://grapesjs.com/docs/modules/Blocks.html#...
GJS Helper
You've accurately identified a discrepancy between the GrapesJS documentation and its TypeScript type definitions for the content property within BlockProperties. This is indeed a bug in the type definition, as the content property is desi...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122 Reproducible demo link https://grapesjs.com/docs/getting-started.html#style-manager Describe the bug How to reproduce the bug?Go to the "StyleManager" section of the "Getting Started" doc from GrapeJSTry to use...
bernesto
Hi @artf, The root issue is that we are trying to place a popover palette absolutely positioned over another element at an arbitrary location on the page. And we need to do this even when the origin element is outside of the editor contain...
artf
@bernesto can you check this one as it seems to be related to your changes
bernesto
Yes, I see the issue. The logic needs to account for when the parent is outside of the container. Let me see what I can do there.