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.
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122 Reproducible demo link https://jsfiddle.net/n38vbktg/ Describe the bug How to reproduce the bug?Create a component that propagates defaults that include layerable = true. Introduce a comment under the competent...
artf
Good catch @bernesto
GJS Helper
This is a valid bug report. The issue arises because GrapesJS's component system, particularly when layerable: true is propagated, attempts to process HTML comment nodes as if they were standard HTML elements. This leads to errors when met...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Version 122.0.6261.95 (Official Build) (64-bit) Reproducible demo link https://jsfiddle.net/n4x6L1v0/2/ Describe the bug How to reproduce the bug?Save component data from an earlier version of grapejs (0.18)Attempt...
artf
Thanks @mitcht but as I already mentioned the main component could never been textnode in the first place so it doesn't make sense to handle such a case in the core or have this issue open. Anyway, if the logic works for you just use it in...
GJS Helper
The issue you're encountering is a known breaking change related to the evolution of GrapesJS's internal component architecture, specifically how the root component of a frame is handled. In older versions (like 0.18), the default root com...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link https://jsfiddle.net/szLp8h4n Describe the bug How to reproduce the bug?Insert <a> tag with link inside the table cell(td).give float left or right to the table cell(td). What is the expected...
artf
Provide valid reproducible demo
GJS Helper
The issue you're encountering where a <td> element changes its display behavior (appearing as a table-row or table-body) when float: right or float: left is applied is not a bug specific to GrapesJS. Instead, it's a fundamental behavior of...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Version 121.0.6167.139 (Official Build) (x86_64) Reproducible demo link none. Describe the bug How to reproduce the bug?add customRte and set breakpointsclick step out until it reaches the logic in ComponentTextView What i...
artf
I can only suggest to check properly the source map path <img width="346" alt="Screenshot 2024-02-12 at 08 45 32" src="https://github.com/GrapesJS/grapesjs/assets/11614725/ee135460-a758-4aef-96fa-1d1b463c934d"> For example, it won't work i...
GJS Helper
It appears you're encountering an issue where the sourcemap for ComponentTextView isn't loading in your browser's DevTools, even though RichTextEditorModule's sourcemap seems to be working. This is a common point of confusion when debuggin...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link None Describe the bug How to reproduce the bug?As per the definition for sectors in https://github.com/GrapesJS/grapesjs/blob/5c890449a52f526bc480d6dc649ff5e01ec59140/src/stylemanager/index.ts...
GJS Helper
You've accurately identified a type definition inconsistency in GrapesJS. The issue stems from a mismatch between the declared type for StyleManagerConfig.sectors.properties in src/stylemanager/config/config.ts and its actual usage and int...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Edge last version Reproducible demo link https://grapesjs.com/demo Describe the bug How to reproduce the bug?Open demo linkClick on HeaderChange view to mobile or tablet.Try to remove background from header. What is the ex...
artf
not a bug but a missing feature, we'll need to extend the stack type with a new configuration for "empty" values. I'll try to bring it in the next version.
artf
the clear icon from de property Background removes completely the properties from the selected device making it inherit again the values from the desktop settings. Correctthe clear icon in the layer line resets the stack values, setting th...
gustavohleal
I've inserted a solution for the stack type. I'm going to make a PR but I would like to ask you something first. The behavior i'm adding is:the clear icon in the layer line resets the stack values, setting the properties for the selected d...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Latest Version Reproducible demo link N/A( I can share video if required for further conversation) Describe the bug How to reproduce the bug?Suppose you have some content on your current page with some styles over t...
afrinxnahar
It would be great if you could kindly attach a video. Not sure about the empty pop-up thing
artf
@prateekkumar-ec this is not core related issue.
GJS Helper
This is a known issue related to how the GrapesJS core:import-code command handles empty CSS input, especially in multi-page setups. When the import button is clicked and the CSS input field in the popup is left empty, the command internal...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Edge v119.0.2151.72 Reproducible demo link https://grapesjs.com/demo.html Describe the bug Hi, thank you for creating an amazing project. I would like to report an issue found during my use of GrapesJS. How to reproduce th...
artf
Agree with the suggested alternative, I will update accordingly. Thanks @duydvu
GJSBlock
Thanks for reporting this, @duydvu. Great question about Performance issue when adding more than 20 classes to a single component. The recommended approach with StyleManager is to use the event-driven API. Start here: Check the GrapesJS do...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefox Reproducible demo link https://jsfiddle.net/497zkrpm/1/ Describe the bug How to reproduce the bug?Select the "Hello World" componentOpen the Style Manager and make sure "myclass" is checked in the classes sectionCh...
artf
Not a bug, the style manager handles only one rule at a time, if you want more advanced usage, you can use the API and implement your functionalities (eg. selecting different rules with the same selector)
MaxDBenson
Not a bug, the style manager handles only one rule at a time, if you want more advanced usage, you can use the API and implement your functionalities (eg. selecting different rules with the same selector) I see. Would you mind elaborating...
GJS Helper
The issue you've encountered with the GrapesJS Style Manager not displaying all rules for the same class is a known behavior stemming from how the editor's internal CssComposer and StyleManager interact with CSS rules. While CSS itself all...