Replies: 2 comments 1 reply
-
Honestly, I'd not expect to see the previous picker, are you able to create a reproducible demo? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Sorry , should have done that in the first place. check it out, notice the default is still usable (have to scroll right) All the best |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've successfully created a new color input type for the StyleManager using the docs.
All works fine (using this) and the added functionality is brilliant (I can change the palette at runtime).
I started to then redefine the style manager properties to then include the new picker. Then realised I can just override the existing by adding the new type with the id as "color":
editor.StyleManager.addType('color', { ... })
This also works, but the existing color picker is not removed, instead they become stacked and both pickers are useable.
Hidden the old ones with:
.gjs-field-color { display: none !important; }
Is this going to cause any issues or is it best to just define a new stylemanager type and redefine all the properties that used the old color picker?
All the best
Beta Was this translation helpful? Give feedback.
All reactions