-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Empty state tables should not show headings #20771
Comments
Could you please resend the image? I’m unable to open it. |
That was posted in the summer of 2024; I work with a lot of graphics. I don't know which one it would be, if I even still have it locally. It seems like it was a screenshot, which could've even been pasted directly from capturing it, forgoing a save to disk (you can copy from Firefox screenshots and paste into GitHub). I don't know why GitHub dropped the image from both here and in the PR. Sorry. It seems like they had a bug in storage somehow. But the context is that empty state tables should never have headings. Here's a screenshot of the accounts page, with a filter searching for "example" which doesn't match a user on my system, and the empty state has a heading... and it shouldn't. I would guess the missing screenshot probably looked like this: It should look something like this quickly modified version of the screenshot: |
Hi @garrett I would like to explore this issue. I think account-list.js is the right place to work on. |
This requires some more non-trivial work with larger implications, that page and other pages use a |
Should I try to do a workaround for this or leave it for now? |
@jelly I'll try to make some changes locally to test things out and see what happens. I'll let you know once I have some updates |
Yes, it should generally be like this for all tables. |
Example in the accounts page:
Originally posted by @garrett in #20763 (comment)
I'm not sure if other parts of Cockpit have headings when tables have empty states. Many (most? all other?) other places to not.
The text was updated successfully, but these errors were encountered: