Skip to content

[UI & UX] Increase component size for namespaces dropdown #6405

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

Open
rmeloca opened this issue Aug 28, 2021 · 8 comments · May be fixed by #10162
Open

[UI & UX] Increase component size for namespaces dropdown #6405

rmeloca opened this issue Aug 28, 2021 · 8 comments · May be fixed by #10162
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@rmeloca
Copy link

rmeloca commented Aug 28, 2021

What would you like to be added

For a large cluster with many namespaces is quite painful to switch between namespaces due to the really tiny size of the component.
It would be nice IMO to have it three times larger.

Why is this needed

To enhance User Experience when switching between namespaces

@rmeloca rmeloca added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 28, 2021
@floreks
Copy link
Member

floreks commented Aug 28, 2021

That's basically why the input field works as a filter, so that user don't have to scroll forever to find the namespace. It is also the default size defined by the material design. We really don't like to override their defaults if this isn't absolutely necessary.

@rmeloca
Copy link
Author

rmeloca commented Aug 28, 2021

I do not disagree with you,
but it is just annoying to me having to leave my mouse just go to the keyboard to type the namespace I want and then switch back to my mouse.

@nneul
Copy link

nneul commented Nov 14, 2021

image

The material design "defaults" are broken in my view if they result in something this badly formatted.

The height of the alarm panel isn't anywhere near that short - why is the namespace list so short - and why so much excessive padding around every line.

.mat-select-panel {
   max-height: 600px;
}

by itself is a huge improvement in usability. Absent a code change - is there any good/easy way to add custom CSS during deployment?

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 12, 2022
@maciaszczykm maciaszczykm added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Feb 15, 2022
@maciaszczykm
Copy link
Member

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 15, 2022
@ashutosh887
Copy link

/assign

@Deepsresthi
Copy link

/assign

@Deepsresthi Deepsresthi removed their assignment Jun 3, 2024
@nh-mike
Copy link

nh-mike commented Jan 28, 2025

Hi folks,

Apologies for posting a link to my own repo, but this has been bothering me too, so I decided to do something about it myself, and created my own container to update the dropdown to 700px. This may be useful for others so I am sharing

This is currently hard coded but if there's sufficient interest, and this current issue does not become resolved, I may look at adding a couple more options.

Currently I am only targeting the latest dashboard-web image. If there's interest for me to target specific tags, I may consider this also.

https://github.com/nh-mike/kubernetes-dashboard-tall-namespace

Cheers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants