You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gradients: custom gradients should be enabled independently from defaultGradients (#36900)
* Gradients: Enable adding custom gradient when gradients are disabled
* Simplify fix by moving check to where we determine multiple origins, add storybook and changelog entries
* Fix issue with custom and customGradient settings not being loaded in ColorEdit
* Hide clear button if there are no gradients and the custom gradient is disabled
* Revert to access color props specifically
Co-authored-by: André <[email protected]>
Copy file name to clipboardExpand all lines: packages/components/CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,7 @@
4
4
5
5
### Bug Fix
6
6
7
+
- Fixed `GradientPicker` not displaying `CustomGradientPicker` when no gradients are provided ([#36900](https://github.com/WordPress/gutenberg/pull/36900)).
7
8
- Fixed error thrown in `ColorPicker` when used in controlled state in color gradients ([#36941](https://github.com/WordPress/gutenberg/pull/36941)).
8
9
- Updated readme to include default value introduced in fix for unexpected movements in the `ColorPicker` ([#35670](https://github.com/WordPress/gutenberg/pull/35670)).
9
10
- Replaced hardcoded blue in `ColorPicker` with UI theme color ([#36153](https://github.com/WordPress/gutenberg/pull/36153)).
0 commit comments