-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Need for compact inputs / components #7704
Comments
Yeah we should evaluate if we need min-widths on input components. Or maybe change it depending on component size. I've brought this topic up with the team today so hopefully we can get some traction on it soon. Related issue: #6202 |
I agree, unless the visuals of the component are changed under a certain width, input components should simply fill 100% of their container. That way, a small width can be specified on the container and the inputs will shrink to fit, without a
|
@tw15egan for the |
We are very limited in space provided in an iframe to 266x699 so having absolute control over spacing is necessary. Overriding CSS becomes excessive and seems to undo the benefits of using a design framework. I'd even go as far as asking for xxs where minimum padding and margins are used allowing us to add back what is needed to improve the view and giving us control over component placement, alignment. |
Summary
The current component designs are very limiting in how interface can be designed. Particularly produtivity (web)applications are suffering strongly from these limitations. There is strong need for more compact versions of the components (whether it be through a prop or an overall feature flag).
Justification
Picture a sidepanel with number inputs – a fairly common UX pattern. Take a look at Keynote, Sketch or Figma for example.
When using the smallest available number inputs (32px high, 150px wide) and a spacing of 8px in between, the width of the
sidepanel is 213% of the size of sketch's sidepanel. A sidepanel with this width is not feasible and wouldn't even fit in the
sm
breakpoint."Must have" functionality
Offer compact versions of components, reducing their inner paddings and min-widths. Potentially find altermative solutions for validation messages to keep the width down).
The text was updated successfully, but these errors were encountered: