Reactivity bug in web UI login form #8755
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
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
The text was updated successfully, but these errors were encountered: