-
Notifications
You must be signed in to change notification settings - Fork 21
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
Adjustments to action td on tables #3075
Comments
Dm'd for more info on the ACs and mild edits, once resolved this will be marked as ready. |
@abroddrick I updated this ticket to add some changes to the table widths. |
@abroddrick when this comes up for design review, can we make sure me and @kristinacyin are added as design reviewers? thanks! |
Feedback from @rachidatecs @gabydisarli or @kristinacyin any thoughts on the feeback from rachid mentioned above? Throwing refinement on it to make sure these are answered. |
@abroddrick I adjusted AC 2 to be a little less prescriptive and more clearly communicate what the desire behavior is. From my understanding, AC 4, 5, and 6 are still relevant. The Action column is one on Domains but not Members. |
And the Action tds still need that max width set. If it's easier, you can adjust the ticket to just say to work with me on the adjustments needed. |
Removed refinement - @CocoByte and @gabydisarli are coordinating on outstanding questions. |
Issue description
The tables across org and non-org model need to be adjusted so they don't stretch so wide. Currently, we're seeing a lot of extra white space between table items, this is leading to a hard to scan table and a visually unpleasing interface. The space between the action td(Edit/View/Manage) and the kebab increases when the user stretches the screen; however, we want that width to stay the same no matter how they adjust their screen to maintain consistency.
Acceptance criteria
Additional context
Slack Thread on the topic of adjusting the action td
Slack thread on discussing the width of tables
Links to other issues
No response
The text was updated successfully, but these errors were encountered: