I have issues with colopicker strugling with proper color convertions
Question
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?
Answers (2)
Thanks for the report. This should have been fixed here https://github.com/GrapesJS/grapesjs/pull/6672
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 have this fixed or those utiliies exposed for customization. Thank you.
Related Questions and Answers
Continue research with similar issue discussions.
Issue #2221
Could anyone give me a proper guideline for making cell components in blockmanager which add others components inside them (Like coumn1, column3/7 and vise versa)
WARNING READ and FOLLOW next 5 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grape...
Issue #3515
BUG: gjs-selected Style is Hardcoded
This definition: https://github.com/artf/grapesjs/blob/88249c38577852dc3c42047356a70a12066ee6ca/src/canvas/view/FrameView.js#L303-L306 is a...
Issue #3596
BUG: Values are not escaped
GrapesJS code is open to XSS issues because values are inserted into DOM without escaping, e.g. https://github.com/artf/grapesjs/blob/dev/s...
Issue #3130
[Question] Standard approach in slight restructuring the HTML toolbar & badge
Version: 0.15.10 This question is intended to validate if there is a proper way to extend the current https://github.com/artf/grapesjs/blob...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.