Issue #4704Opened November 2, 2022by PaulSchult0 reactions

BUG: Angular Component as Custom Color Picker is only created once

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Version 104.0.5112.101

Reproducible demo link

https://codesandbox.io/s/awesome-dewdney-bwo5t1

Describe the bug

How to reproduce the bug?

  1. Add the Text block to the content of the editor
  2. Open the StyleManager and expand the Decorations Sector
  3. Notice the red placeholder text where normally the standard color picker is located (this text is a basic angular component)
  4. Next, scroll down to the "Background" tab and add a new background
  5. Notice again the red placeholder text
  6. Click on the main content of the grapes content, so the styleManager switches to the settings of the body
  7. Now click on the text block again and scroll down to the background tab and expand it
  8. Notice how the placeholder text for the color attribute isn't there
  9. If you look in the console of the browser you see that the angular component got destroyed when selecting another element, but never got created again

What is the expected behavior? The Angular Component should be created/rendered again when opening the Background Tab.

What is the current behavior? The Angular Component is destroyed when the Background Tab closes and we lose the ability to change the color until the whole grapes editor is opened again.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (0)

No answers yet.

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...

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.