-
Notifications
You must be signed in to change notification settings - Fork 14
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
Table: do we need to expose the pixel size? #980
Comments
FYI @gtk-grafana . You probably thought about this one and there may be a challenge on the fix, but it's a bit deterrent of using the table viz (at least for me). In addition, do you think it's worth to expose the pixel size to the user? Clearing the width seems ok, but the exact amount of pixels seems like unnecessary information. |
Yeah the line field should use all of the available space (minus the width of the other columns), unless one has been defined manually by resizing the column via drag-n-drop, then you'll see this. It might be better to add an additional icon to the columnheader to let folks clear out the defined width instead of tucking that away. And agreed, exposing the pixel size is probably not needed, and confusing. |
Ahhhh! I probably set it at some point without realizing. Cool. Maybe just skip the pixel size, then. |
I think you made a good point though, if you accidentally resize something you have to dig around in the UI to fix it, should be something that displays top-level to let users clear the custom column size. If you ran into this I'm sure it's frustrating some users as well |
We are currently exposing the pixel size of the columns to the user, which seems like very specific and unnecessary information.
In addition: should the widths auto update size when adding/removing columns?
The text was updated successfully, but these errors were encountered: