https://github.com/GrapesJS/grapesjs/blob/f59e981f76ff378f59c06cf706af88e502db098e/packages/core/src/utils/ColorPicker.ts#L2407C5-L2415C6 I traced back to these lines and seems like when converting HEXA to RGBA theese lines mess up results. Is there particular reason to intentionally support legacy ARGB?
artf
Thanks for the report. This should have been fixed here https://github.com/GrapesJS/grapesjs/pull/6672
yvoroniak-infusemedia
for ex: #ff000077 (transparent red) is being converted to #000077 (shade of blue). I tried monkey patch it but seems like internaly grapes js uses its own implementation not the one bound to window. (unfortunately for me) Would be nice to...
GJS Helper
The issue you've identified regarding the GrapesJS ColorPicker struggling with proper color conversions, specifically from HEXA to RGBA, and your observation about potential legacy ARGB support, points to a common misunderstanding of hexad...
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? chrome v91 Reproducible demo link https://codepen.io/asenper/pen/QwNMwpV Describe the bug I expect the RTE to open when clicking on the text, but nothing happens. Is this a bug or am I missing additional configuration? Cod...
artf
By default the text component is activated with a double-click https://github.com/GrapesJS/grapesjs/blob/f59e981f76ff378f59c06cf706af88e502db098e/packages/core/src/dom_components/view/ComponentTextView.ts#L22
When you import generic HTML it's hard to detect text components properly. If you have the ability to edit HTML you can enforce it via gjs attributes <div data-gjs-type="text">Insert....
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 136.0.7103.93 Reproducible demo link https://jsfiddle.net/j826eL51/ Describe the bug How to reproduce the bug? Follow the steps in the Getting Started page When you get to Add Blocks, the blocks don't appear. What i...
artf
Thanks for the report @jaredtmartin
GJS Helper
The issue you're experiencing, where blocks do not appear when following the GrapesJS "Getting Started" guide, stems from a misconfiguration in your grapesjs.init options, specifically related to how the blockManager and panels are set up....
Feature Description Add support for dark mode in the editor interface. Motivation Reduce eye strain during night-time development Match modern UI/UX standards Support system-level dark mode preferences Proposed Implementation Add dark mode color palette Create theme switching mechanism Persist user preference Add syst...
artf
same as here
GJS Helper
Adding dark mode support to GrapesJS involves a combination of CSS theming, JavaScript for theme switching and persistence, and integrating with system preferences. While GrapesJS doesn't have a built-in dark mode toggle, its modular natur...
Description The navigation menu is not properly responding to screen size changes on mobile devices. Steps to Reproduce Open the page builder Add a navigation menu component Preview on mobile device or resize browser window Observe the menu behavior Expected Behavior Menu should collapse into a hamburger menu on mobil...
artf
Hey @brighterfrog it's important to follow the template of the bug report. Please open a valid bug report (with a reproducible demo).
GJS Helper
The issue you're encountering with the GrapesJS navigation menu not being responsive on mobile devices is a common challenge, as GrapesJS primarily provides the structural components. Achieving a fully responsive, collapsing navigation men...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefix v132.0 Reproducible demo link https://jsfiddle.net/skdegqun/4/ Describe the bug How to reproduce the bug?Running the fiddle can be appreciated on the logs that the data sources passed on editor initialization were...
artf
You need to wait until the editor is ready.
GJS Helper
The issue you're encountering is a known behavior where the GrapesJS DataSources module does not automatically hydrate its state from the dataSources property within the projectData during editor initialization or when loading from storage...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? ChromeReproducible demo link ---Describe the bug editor.getModel().initBaseColorPicker(DomElement, { / spectrum options / }); after initailization when the palete opens i want to set a color to it ? @artf Code of Conduct[X]...
NeonLexie
This looks interesting. I wouldn't mind taking a crack at it.
yashvi2026
GJS Helper
To set an initial color for a custom color picker initialized with editor.getModel().initBaseColorPicker(), you need to pass the color option within the Spectrum.js options object. GrapesJS's initBaseColorPicker method internally uses Spec...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome latest Reproducible demo link https://codesandbox.io/p/sandbox/withered-rgb-xmw8gk Describe the bug How to reproduce the bug?Open code sandboxSelect "body" (type: 'wrapper') - observe alert about getting value from...
padcom
Thank you! I verified and it is working as expected!
padcom
From what I can see the Trait.setValue() is not called when the value comes from an input. Instead the setTargetValue() is called which doesn't check if the setValue() method of the trait definition is there. Also, the Trait.setValue() che...
padcom
I tried following this discussion to get it working but as you can see in the sandbox it just doesn't work.
To create a custom GrapesJS component with editable text, an editable image, and custom styling options, you need to define a new component type using editor.DomComponents.addType and then register it as a block. This allows users to drag...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 128 Reproducible demo link https://jsfiddle.net/sammousa/bxgsdc12/11/ Describe the bug How to reproduce the bug?Load an HTML string with a non empty <head>, using the option {asDocument: true}.Export the data via ed...
SamMousa
Thank you, but that's not really the point. I'm fully able to make a workaround, but that does not fix the bug. The bug is that an export via getProjectData() followed by an import via loadProjectData() should result in the same state. Fur...
artf
The bug is that an export via getProjectData() followed by an import via loadProjectData() should result in the same state. Yeah definitely not expected, we'll look into it. Appreciate the easily reproducible steps on the demo ๐
artf
Thanks @SamMousa detailed bug reports are always welcome. If a direction is requested, we're happy to guide you ๐โโ๏ธ