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
Several components (e.g. InputControl and family) have a __unstableInputWidth prop, which has been experimental for very long. This prop is required for labelPosition="edge" to work (labelPosition is a stable prop).
SelectControl has a labelPosition prop, but the "edge" option cannot be utilized correctly because the __unstableInputWidth prop is not exposed.
It's also important to note that the labelPosition prop is barely used, aside from "top" which is the default. There are only two use cases in the Gutenberg app (both are "edge"). There is not a strong need for this feature.
__unstableInputWidth itself, independent of labelPosition, is used a little bit more. But still not a lot.
What is your proposed solution?
Assess if we really want to stabilize this, or if we would prefer consumers to do custom layouts in a more modular way.
The text was updated successfully, but these errors were encountered:
What problem does this address?
Several components (e.g.
InputControl
and family) have a__unstableInputWidth
prop, which has been experimental for very long. This prop is required forlabelPosition="edge"
to work (labelPosition
is a stable prop).SelectControl
has alabelPosition
prop, but the"edge"
option cannot be utilized correctly because the__unstableInputWidth
prop is not exposed.It's also important to note that the
labelPosition
prop is barely used, aside from"top"
which is the default. There are only two use cases in the Gutenberg app (both are"edge"
). There is not a strong need for this feature.__unstableInputWidth
itself, independent oflabelPosition
, is used a little bit more. But still not a lot.What is your proposed solution?
Assess if we really want to stabilize this, or if we would prefer consumers to do custom layouts in a more modular way.
The text was updated successfully, but these errors were encountered: