Issue #3260πŸ’¬ AnsweredOpened February 3, 2021by mhowey1 reactions

Color Picker Transparency slider is at 0 in firefox.

Quick answerby mhowey❀ 1

@artf Another difference to note between Firefox and Chrome is what is displayed in the palette. Firefox shows a transparent box while Chrome shows a gray one.

Read full answer below ↓

Question

The color picker in grapesjs does not work the same between Chrome and Firefox. When you open the picker on a selected component that has never had it's background color set before (for instance...) the color picker opens with opacity set to 100% in Chrome and 0% in Firefox.

The issue is that the user may hot even look at this transparency slider when using Firefox and will try to change colors unsuccessfully, not realizing that the opacity is at 0%.

Expected Behavior: In all browsers the color picker will open with the transparency set to 100% by default when the component that is being styled has never had its background color specified.

Actual Behavior: In Chrome, the color picker works as expected. In Firefox the color picker always initially opens with the opacity slider at 0%.

Thanks in advance for your great project!!

Version: Latest

You can get the version by typing grapesjs.version into the console

Are you able to reproduce the bug from the demo?

[X] Yes

Answers (3)

mhoweyβ€’ February 4, 2021

@artf Another difference to note between Firefox and Chrome is what is displayed in the palette. Firefox shows a transparent box while Chrome shows a gray one.

artfβ€’ July 27, 2023

Seems to be solved on the latest Firefox version

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @mhowey.

The issue with Color Picker Transparency slider is at 0 in firefox. appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.

What to try:

  1. Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
  // your operation here
}, 0);
  1. Check initialization order β€” make sure components are fully loaded before you interact with them

  2. Use the editor's event system β€” listen to completion events:

editor.on('component:mount', (component) => {
  // safe to interact with component here
});

Recommended next steps:

  • Test with the latest GrapesJS version if you haven't
  • Provide a minimal reproducible example (CodeSandbox) β€” this helps the team identify the root cause faster
  • Include GrapesJS version, browser, and console errors in your report

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins β†’
Premium option

Premium plugins ship with support, regular updates, and production-ready features β€” save days of integration work.

Browse premium plugins β†’

Related tutorials

In-depth guides on the same topic.

All tutorials β†’

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.