Reactivity bug in web UI login form

[jnoordsij]

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

[maciaszczykm]

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

[floreks]

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

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[jnoordsij]

/remove-lifecycle stale

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[jnoordsij]

/remove-lifecycle stale

[lsq645599166]

/assign