Skip to content
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

Open
janhassel opened this issue Feb 1, 2021 · 4 comments
Open

Need for compact inputs / components #7704

janhassel opened this issue Feb 1, 2021 · 4 comments
Labels
adopter: PAL Work-stream that directly helps a Pattern & Asset Library. package: @carbon/react @carbon/react proposal: accepted This request has gone through triaging and we are accepting PR's against it. type: enhancement 💡 version: 11 Issues pertaining to Carbon v11

Comments

@janhassel
Copy link
Member

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.

image

"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).

@aledavila aledavila added proposal: open This request has gone through triaging. We're determining whether we take this on or not. and removed status: needs triage 🕵️‍♀️ labels Feb 1, 2021
@aagonzales
Copy link
Member

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

@tw15egan
Copy link
Collaborator

tw15egan commented Mar 5, 2021

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 min-width preventing that. I think this can be broken into two different issues

  • Removing min-width on form components
  • Provide an xs size variant to reduce the overall height

@janhassel
Copy link
Member Author

@tw15egan for the xs size it would be helpful to reduce the component's padding. The number input currently uses spacing-05 I think, which could be reduced to spacing-03 maybe?

@wnm3
Copy link

wnm3 commented Mar 18, 2021

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.

@tay1orjones tay1orjones added proposal: accepted This request has gone through triaging and we are accepting PR's against it. and removed proposal: open This request has gone through triaging. We're determining whether we take this on or not. labels Nov 8, 2021
@tay1orjones tay1orjones moved this to 🕵️‍♀️ Triage in Design System Nov 8, 2021
@tay1orjones tay1orjones moved this to Accepted in Roadmap Aug 24, 2022
@sstrubberg sstrubberg moved this from Accepted to Condensed in Roadmap Oct 11, 2022
@tay1orjones tay1orjones moved this from 🕵️‍♀️ Triage to 🪆 Needs Refined in Design System Dec 6, 2022
@sstrubberg sstrubberg added package: @carbon/react @carbon/react adopter: PAL Work-stream that directly helps a Pattern & Asset Library. adopter: DSAG version: 11 Issues pertaining to Carbon v11 labels Dec 7, 2022
@sstrubberg sstrubberg moved this from Condensed Epic to Icebox in Roadmap Dec 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
adopter: PAL Work-stream that directly helps a Pattern & Asset Library. package: @carbon/react @carbon/react proposal: accepted This request has gone through triaging and we are accepting PR's against it. type: enhancement 💡 version: 11 Issues pertaining to Carbon v11
Projects
Status: Later 🧊
Development

No branches or pull requests

7 participants