GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 142.0.7444.61 Reproducible demo link https://codepen.io/DavidHarvey-the-lessful/pen/ZYWeMbG Describe the bug Component droppable status is ignored when moving a textable component into a text component. How to repro...
The issue you've encountered where droppable: false on a GrapesJS text component is ignored when a textable component is dragged into it is a known behavior stemming from how GrapesJS integrates its Rich Text Editor (RTE) and handles texta...
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Version 141.0.7390.123 (Official Build) (64-bit) Reproducible demo link https://codesandbox.io/p/sandbox/jovial-elion-js8zgy?file=%2Findex.js%3A1%2C1-15%2C1 Describe the bug The above worked in 0.15.x but not in 0.22.13. A...
artf
Hey @bilogic your demo seems to use the proper API for extending components, the one relying on .extend( was dropped a long time ago
GJS Helper
The issue you're encountering when extending a GrapesJS component model, specifically the 'link' type, and trying to set its defaults property by directly referencing linkType.model.prototype.defaults is a change in behavior between Grapes...
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? chrome latest version Reproducible demo link https://app.grapesjs.com/studio Describe the bug How to reproduce the bug? Initialize GrapesJS editor with default device configuration Switch to tablet or mobile device view Ad...
GJS Helper
The issue you've described is a known behavioral change introduced in GrapesJS v0.22.10+, where default component styles are incorrectly applied to device-specific media queries when a component is added while a non-desktop device view is...
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? 140.0.7339.214（正式版本） (x8664) Reproducible demo link https://codesandbox.io/p/devbox/d27l6n Describe the bug I want to create a custom dynamic list component based on GrapesJS (with 3 rows by default). It can bind to an arr...
GJS Helper
The freezing issue you're encountering with your custom Dynamic List component in GrapesJS is a classic example of an event feedback loop. It occurs because the event listener responsible for updating the row count is too broad, causing it...
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Firefox Reproducible demo link https://grapesjs.com/demo.html Describe the bug Description The editor has very slow loading times. On complex pages (e.g. homepage with many elements and plugins such as carousels), it can t...
artf
Thanks @MisterKeyboard for providing the JSON. Your project contains 10K style rules, which is a lot, but still, I'd not expect the load to be impacted that much. @mohamedsalem401 I think we need to verify if data source related changes (e...
mohamedsalem401
@artf Will take a look and give an update on this.
artf
@MisterKeyboard can you share the JSON of the project so we can verify that
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v142.0.7392.0 (canary) Reproducible demo link https://jsfiddle.net/xce183nm/1/ Describe the bug How to reproduce the bug? Create an editor instance and load HTML code that contains character references in attribute...
artf
Thanks for providing all the info and details, that was helpful. Thanks also for the PR.
GJS Helper
You've identified a critical bug in GrapesJS's HTML serialization process regarding attribute value escaping. The issue stems from the Component model's renderAttributes method, which directly inserts attribute values into the HTML string...
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/zxvREjB Describe the bug How to reproduce the bug? Drag and drop the text component What is the expected behavior? It should not be selected /dragged in layerma...
artf
You can hide the component from layers with layerable: false property or create your own custom layer manager UI with all the UI logic you need.
GJS Helper
The issue you're experiencing where locked components can still be selected, dragged, and deleted in the GrapesJS Layer Manager is a common point of confusion. The locked property on a GrapesJS component primarily controls interactions on...
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Firefox Developer 142.0b9, Chrome 138.0.7204.184 Reproducible demo link https://jsfiddle.net/artur_arseniev/ta19s6go/ Describe the bug How to reproduce the bug? Make the "Article" component a symbol Add a text component to...
GJS Helper
The issue you've described, where adding a text component to an original symbol instance leads to cursor resets, flickering, and continuous component:add events, is a known interaction conflict between GrapesJS's symbol update mechanism an...
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Edge: Version 135.0.2535.51 (Official build) (64-bit), Chrome: Version 135.0.6422.112 (Official Build) (64-bit) Reproducible demo link https://app.grapesjs.com/studio?utmsource=grapesjs&utmmedium=mainTopNav Describe the bu...
msftedad
Hi Team, Any update on this issue?
GJS Helper
The issue you've reported highlights a common accessibility challenge in web builders that rely heavily on drag-and-drop interactions. GrapesJS, by default, implements its block and component manipulation primarily through mouse/touch-base...
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrom v140.0.7307.0 (canary) Reproducible demo link https://jsfiddle.net/y3gr69s4/ Describe the bug How to reproduce the bug? Create editor instance with parser.optionsHtml.keepEmptyTextNodes option set true. Load HTML cod...
GJS Helper
You've accurately identified a discrepancy in how the keepEmptyTextNodes option is handled in GrapesJS, leading to newlines being stripped from your HTML output. This is indeed a bug related to the parser's configuration and its TypeScript...