Custom duotone menu has disappeared

[webexpr-dhenriet]

Description

Impossible to create a specific duotone.
I can only choose from the duotones available.
The creation menu has disappeared.
In theme.json settings.color.customDuotone is set to true.

Step-by-step reproduction instructions

• admin
• select image, duotone

Screenshots, screen recording, code snippet

Environment info

• WP 6.4.3

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

[carolinan]

Hi
I am not able to reproduce this.
I am getting different results depending on if Gutenberg 17.6 is active and wether I am using a classic theme.
But the custom selector works in all my tests.

customDuotone defaults to true, so you don't need it in theme.json.
https://developer.wordpress.org/block-editor/reference-guides/theme-json-reference/theme-json-living/#color

On WordPress 6.4.3 or 6.3.3:
Classic theme, Twenty Twenty: The custom duotone selector works, but the WordPress default Duotones are not available.
Twenty Twenty-Four: Site Editor and post editor: The custom duotone selector work, the theme duotones work, and the WordPress default Duotones are not available. The theme has "defaultDuotone": false,.

On WordPress 6.4.3, or 6.3.3 with Gutenberg 17.6 active:
Classic theme, Twenty Twenty: The custom duotone selector work, and the WordPress default Duotones work.
Twenty Twenty-Four: Site Editor and post editor: The custom duotone selector work, the theme duotones work, and the WordPress default Duotones are not available. The theme has "defaultDuotone": false,.

On WordPress 6.5 alpha
Classic theme, Twenty Twenty: The custom duotone selector work, and the WordPress default Duotones work
Twenty Twenty-Four: Site Editor and post editor: The custom duotone selector work, the theme duotones work, and the WordPress default Duotones are not available. The theme has "defaultDuotone": false,.

[webexpr-dhenriet]

@carolinan thanks for your feddback.
I am using a custom hybrid theme (PHP,theme.json) without Gutenberg plugin. I'll try to clear this up as soon as I have a bit of time.

It's just an ux problem.
It seems to me that the custom duotone used to be accessible from the right-hand sidebar.
This custom duotone menu (shadow) is only accessible from the top bar of the element.
Has this changed?

---

[graylaurenm]

I'm seeing the same in my custom Block theme. I have "defaultDuotone": false, and typically am able to create custom duotones with my color palette (I have the default and custom color options disabled). I do not have the Gutenberg plugin installed, so this is from the core update imo. I may be able to provide more detailed troubleshooting tomorrow.

[carolinan]

Hmm you know what, I only tested the toolbar option. I will try to find the time to do another round of testing.

[graylaurenm]

I can replicate this in a fresh WordPress install using TT4. The toolbar has custom duotone options, the sidebar block styles do not.

Correct:

Missing:

[t-hamano]

I was able to reproduce the problem mentioned in this comment in TT4.

• Reproduced in WordPress 6.5 Beta1.
• Reproduced on WordPress 6.5 Beta1 with Gutenberg version 17.7.0 enabled.
• Reproduced in WordPress6.4.3.
• Reproduced not only with image blocks but also with the cover block.

What I can think of from this is that the custom duotone settings may not have been taken into account in the block sidebar.

[t-hamano]

I did some more research and found that the current behavior may be intentional, as seen in #55361. (see this comment)

I hacked this code to temporarily enable custom colors, and they work for individual blocks. However, in the Global Styles, they don't work for blocks.

dfc4b9b391c2182a52ee5ddad3435fc8.mp4

@ajlende @MaggieCabrera Is it possible to enable the custom duotone in the block sidebar as in the block toolbar, but leave the custom duotone disabled at the global style block level?

[github-actions]

Hi,
This issue has gone 30 days without any activity. This means it is time for a check-in to make sure it is still relevant. If you are still experiencing this issue with the latest versions, you can help the project by responding to confirm the problem and by providing any updated reproduction steps.
Thanks for helping out.

[webexpr-dhenriet]

I'am still experiencing this issue with the latest versions.

[github-actions]

Hi,
This issue has gone 30 days without any activity. This means it is time for a check-in to make sure it is still relevant. If you are still experiencing this issue with the latest versions, you can help the project by responding to confirm the problem and by providing any updated reproduction steps.
Thanks for helping out.

[webexpr-dhenriet]

I'am still experiencing this issue with the latest versions.