You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you fill one of the fields required to create a new cluster when using the console UI installer with any automatic form filling applications or browser extensions, the "next" or "create cluster" button will stay disabled. It seems like the validation to check if all fields on the screen has been filled correctly are done with some key events tie the fields.
To be able to move to the next step, one need to click or bring the focus to the problematic field, and add + delete a random letter so the console app detect the input. It is not obvious, one user thought some other information were wrong, and wasn't sure why it seems like his email wasn't valid.
We should check if they have input with other events. May be related to #1921
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Which version of kubefirst are you using?
2.3.5
Which cloud provider?
None specific
Which DNS?
None specific
Which installation type?
UI (Console app)
Which distributed Git provider?
None specific
Did you use a fork of
gitops-template
?No
Which Operating System?
None specific
What is the issue?
If you fill one of the fields required to create a new cluster when using the console UI installer with any automatic form filling applications or browser extensions, the "next" or "create cluster" button will stay disabled. It seems like the validation to check if all fields on the screen has been filled correctly are done with some key events tie the fields.
To be able to move to the next step, one need to click or bring the focus to the problematic field, and add + delete a random letter so the console app detect the input. It is not obvious, one user thought some other information were wrong, and wasn't sure why it seems like his email wasn't valid.
We should check if they have input with other events. May be related to #1921
Code of Conduct
The text was updated successfully, but these errors were encountered: