👋 A new build is available for this PR based on a2c3496.

• Download here.
• Read more about how to test

There is some odd behaviour that I have been able to inconsistently recreate. I set the value to 2000 (or 20,000), double checked the value. Connected to the system successfully. Disconnected, then checked the value again and it seems to have changed the timeout value to 1999 (or was 19,998). I will see if i can consistently recreate it, but so far its sporadic behaviour.

I can set the readyTimeout field to 0, even though it has min set to 1. It shows as red, but the save is still allowed. I checked the settings file and it does save as 0. It does not treat the timeout as 0ms, it seems to just ignore the timeout when it is 0.

In regards to the other issue I mentioned with the timeout value changing, I have been unable to recreate it more than 2 more times after 200+ tries. So it seems to be a possible one off of the string to number conversion. I wouldn't be concerned about it.

Thanks @julesyan !
I fixed the numeric value not being entirely checked - setting a value lesser than 1 will not allow you to save the settings.

As for the odd behavior, I think I found what the "issue" is. Spoiler alert: it's not a bug, it's a feature. 😅
It turns out that if a numeric field has the focus and your mouse pointer it on it, the value will increment/decrement if you use your mouse scrollwheel!

To try to prevent this from happening, I moved the field to the bottom of the form. Since it used to be in the middle, it was natural to use the wheel to scroll down to the Save button, with the risk of changing the value while doing so.

Give it a try and let me know how it goes!

I changed the type of the SSH port number field to a "number" input, so there's a better check on the value.

@julesyan it should be OK now. I used a more global event to catch changes in any input field. Let me know how it goes!

Much obliged @julesyan 🙏🏻