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

fix: UI alignment issues in page tables #1182

Merged
merged 2 commits into from
Jan 18, 2023
Merged

Conversation

deboer-tim
Copy link
Collaborator

What does this PR do?

Fixes the following UI issues on the main page tables, with explanation of each fix:

  • Creation date sometimes appeared on two lines: add whitespace-nowrap
  • Creation date header didn't line up with column: remove header centering, fix padding to match cell, and remove cell left margin.
  • Name header centered on Images and Volumes page but not others: removed centering on these page.
  • Container list column sizes change when you start a container, and when the width of the age text changes: use w-10 for name column so only age column changes width.

Screenshot/screencast of this PR

One example - others should be obvious enough. Before:
Screenshot 2023-01-16 at 10 18 54 AM

After:
Screenshot 2023-01-16 at 10 19 22 AM

Fixed the following issues:
- Creation date sometimes appeared on two lines: add whitespace-nowrap
- Creation date header didn't line up with column: remove header centering, fix padding to match cell, and remove cell left margin.
- Name header centered on Images and Volumes page but not others: removed centering on these page.
- Container list column sizes change when you start a container, and when the width of the age text changes: use w-10 for name column so only age column changes width.

Signed-off-by: Tim deBoer <git@tdeboer.ca>
@cdrage
Copy link
Contributor

cdrage commented Jan 17, 2023

Should we change "Creation Date" to "Age" while were at it so it's similar code-wise to the ContainerList.svelte?

Otherwise, this LGTM! Tested and viewed it. All looks good to me.

@deboer-tim
Copy link
Collaborator Author

FWIW, I couldn't find any design guidance that would lean towards either, and I think there's a slight semantic difference between age and creation date and how we're using it today - i.e. age is only used for how long a container has been running, not when it was created. My preference would be to merge, and I'm happy to change it later if there's agreement.

Copy link
Collaborator

@benoitf benoitf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can do follow-up PR for Age

@benoitf benoitf merged commit 321b1f9 into containers:main Jan 18, 2023
@podman-desktop-bot podman-desktop-bot added this to the 0.11.0 milestone Jan 18, 2023
@deboer-tim deboer-tim deleted the ui-nit branch January 25, 2023 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants