GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Firefox 136.0.1 (64 bits) Reproducible demo link https://grapesjs.com/docs/api/editor.html#editor Describe the bug How to reproduce the bug? Go to https://grapesjs.com/docs/api/editor.html#editor What is the expected behav...
Thank you for reporting this issue. You've correctly identified a bug in the GrapesJS documentation website. Root Cause: The {REPLACEEVENTS} placeholder indicates that the documentation generation process failed to correctly inject the lis...
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? All browsers, latest version Reproducible demo link Can be reproduced on offical demo Describe the bug How to reproduce the bug? Add a block, set the height and min-height to 0 Add another normal block Add a container Try...
GJS Helper
This is a known behavior in GrapesJS related to how its drag-and-drop system (which often relies on visual bounding boxes) interacts with elements that have zero height. While ideally, the drag-and-drop mechanism should be robust enough to...
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? chrome 133 with dev branch as of 02.27.2025 Reproducible demo link clone dev repos as of 02.27.2025 Describe the bug How to reproduce the bug? ... clone repo and build and start ...in demo page click to enter preview mode...
sumasal
temporary workaround for the impatient:
GJS Helper
It appears you've identified a bug in the GrapesJS dev branch where component dragging is still possible even when the editor is in preview mode. This is indeed contrary to the expected behavior, as preview mode should disable all editing...
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Version 133.0.6943.127 (Official Build) (arm64) Reproducible demo link https://grapesjs.com/demo.html Describe the bug How to reproduce the bug? Create a text block Start typing any japanese characters Choose an ent...
GJS Helper
The issue you're experiencing with Japanese input in GrapesJS, where the chosen entry is invisible and an extra return is added, is a common problem in rich text editors that rely on contenteditable and Input Method Editors (IMEs), such as...
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Firefox and Chrome Reproducible demo link I can't do a demo for remote storage Describe the bug Import anything that has > next to a tag with > Example: <a href="#">></a> Also happens like this: <a href="#">Home</a>...
artf
I can't do a demo for remote storage You don't need a demo for remote storage. The local and remote storage are using the same interface, which means if you're not able to reproduce with the locale storage, the problem is probably on your...
GJS Helper
This is a critical bug report. The issue where GrapesJS displays "undefined" and fails to load content when the HTML entity > (greater than sign) is present, especially near HTML tags, indicates a problem with GrapesJS's internal HTML p...
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v133 Reproducible demo link https://jsfiddle.net/2hjdrb7L/1/ Describe the bug How to reproduce the bug? Initialize a grapesjs editor using grapesjs v0.22.x with the grapesjs-touch plugin v0.1.1. What is the expected...
bamiendev
Same issue
federica-capobianco
did you manage to solve it? Facing a kind of similar issue
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Version 133.0.6943.98 Reproducible demo link https://codesandbox.io/p/sandbox/loving-breeze-mdls43?file=%2Findex.js%3A77%2C6 Describe the bug Iam trying to add some custom triats to my block unfortunately i can only see th...
artf
Your component has inner components, so if you select one of those, you will see traits of those components, not event-block. If you properly select event-block, you'll see your traits. <img width="856" alt="Image" src="https://github.com/...
GJS Helper
The issue you're encountering, where custom traits don't load for a custom block when its components property contains complex HTML but do load with a simple string, is a known behavior related to how GrapesJS parses and manages component...
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Safari 18.3 Macos 14.7.3 Reproducible demo link https://grapesjs.com/demo.html Describe the bug How to reproduce the bug? Open the Layer Manager on the right panel Try to hide "body", or open it OR click on an element, the...
GJS Helper
It appears you've encountered a known rendering quirk specific to Safari, particularly with how it handles flexbox layouts and potentially icon fonts within those layouts. The GrapesJS Layer Manager utilizes a flexbox structure for its lay...
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/ZYzjaYe Describe the bug What is the expected behavior? border width should be incremented from 1 when min is set to 1. What is the current behavior? But the va...
GJS Helper
The issue you're encountering with the min value not affecting the initial display of 0 for border-width is a common point of confusion. The min property in GrapesJS style manager primarily affects the stepper/slider controls and validatio...
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/gbYjOWO Describe the bug How to reproduce the bug? I have called onactive on single click so that i can edit the textbox in single click. The cursor should be p...
mohamedsalem401
Hey, I've checked your code and tried to debug it. It seems to me that the code is not passing the mouse event to the onActive method, which is needed: ```js componentEl.addEventListener('click', (ev) => { component.view.onActive(ev); });
GJS Helper
The issue you're experiencing, where the cursor always goes to the beginning of the text box when activating editing on a single click, stems from how contenteditable elements are programmatically activated versus how they behave with nati...