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

Reactivity bug in web UI login form #8755

Open
jnoordsij opened this issue Mar 7, 2024 · 2 comments · May be fixed by #9040
Open

Reactivity bug in web UI login form #8755

jnoordsij opened this issue Mar 7, 2024 · 2 comments · May be fixed by #9040
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@jnoordsij
Copy link
Contributor

What happened?

When logging in (latest version of web UI) and autofilling the token field with my password manager plugin, the value is filled but the Sign in button remains disabled. Only after manually focussing on the field and pressing enter the value is detected and the Sign in button becomes enabled.

What did you expect to happen?

The Sign in button to become enabled as soon as a value is present in the token input field.

How can we reproduce it (as minimally and precisely as possible)?

Programmatically set the token value in any manner (e.g. through a browser plugin).

Anything else we need to know?

I'm pretty sure this worked previously; I have not yet attempted to look for the differences in the UI compared to previous versions myself, but that might be a good place to start.

What browsers are you seeing the problem on?

No response

Kubernetes Dashboard version

7.0.0

Kubernetes version

1.29

Dev environment

No response

@jnoordsij jnoordsij added the kind/bug Categorizes issue or PR as related to a bug. label Mar 7, 2024
@maciaszczykm
Copy link
Member

We will probably need to listen for different event to support password managers.

@maciaszczykm maciaszczykm added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Mar 7, 2024
@floreks
Copy link
Member

floreks commented Mar 7, 2024

Probably it directly overrides the value of the input via code and only triggers a change event. Should be an easy fix.

@r-yabyab r-yabyab linked a pull request May 16, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants