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
While working on #67544 I noticed that we don't really use the BoxControl component much and that it has been forked several times already.
We used to use it for padding/margin. We still use in some conditions for block gap, padding and margin, but most of the time it's not used and instead a custom "Spacing" component is used.
I believe it was also considered for BorderRadius but was discarded. So in the end, we built a component that we don't really use much (and we forked for the original use-cases that it was built for). (Context here is this PR comment).
Proposal
With some small tweaks/features added to the component, we can drop a number of custom components we have right now, these features include:
support for presets (like we already for ColorPalette component for instance)
More customization options (like providing custom icons and labels for the "sides")
All these components should be using BoxControl
cc @WordPress/gutenberg-components
The text was updated successfully, but these errors were encountered:
While working on #67544 I noticed that we don't really use the BoxControl component much and that it has been forked several times already.
We used to use it for padding/margin. We still use in some conditions for block gap, padding and margin, but most of the time it's not used and instead a custom "Spacing" component is used.
I believe it was also considered for BorderRadius but was discarded. So in the end, we built a component that we don't really use much (and we forked for the original use-cases that it was built for). (Context here is this PR comment).
Proposal
With some small tweaks/features added to the component, we can drop a number of custom components we have right now, these features include:
All these components should be using BoxControl
cc @WordPress/gutenberg-components
The text was updated successfully, but these errors were encountered: