-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken preset duotone filters in classic themes #49293
Comments
I went down one WordPress version at a time to determine when this problem started. This problem has been occurring since WordPress 6.0. So it may be a regression that went unnoticed for a long time. |
From my research, I believe this is the intended behavior. The This change is part of #38681 in Gutenberg. |
Thanks for digging that up! Thinking back, #38681 was in response to WP 5.9 adds default Duotones before closing the body. Now that that issue has been more properly resolved, we can probably bring back the default duotone filters in classic themes—they will no longer get added to every page load. Additionally, for filters that don't exist (such as a block theme's custom duotone filters), the fallback behavior should be an unfiltered image rather than an image with a broken filter like is shown in the screenshot. EDIT: I updated the title and description to reflect this. |
Description
When switching from a block theme to a classic theme, preset duotone filters are broken.
I would expect to see a correct filter if a default filter was selected, or no filter if a theme filter was selected (since the preset won't exist on a classic theme).
Additionally, with #49103 merged, preventing default duotone filters from being output on every page, we may be able to bring back the default filters in the duotone selector that were removed in #38681.
Step-by-step reproduction instructions
core/cover
Screenshots, screen recording, code snippet
Environment info
No response
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
The text was updated successfully, but these errors were encountered: