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
{{ message }}
This repository has been archived by the owner on Mar 11, 2024. It is now read-only.
Played around with the lock time in the wallet and found these bugs.
If I type the locktime without mouseclicks i get 6 numbers in the year. example: 19.05.202344 --:--
When I use the arrow keys on the keyboard to go back or forward by 1 year, the number 275760 appears as the year before 2023, maybe it could be stopped by 2023 or the actual year.
After setting the lock time, for example: 20.05.2024 10:00, if I want to correct the year afterwards, it jumps to 1901, and I can only change the last digit, from 1901 to 1909.
When I hover over the field, strangely I get a pop-up in German even though the wallet is set to English. Gib einen gültigen Wert ein, das Feld ist nicht vollständig...
The text was updated successfully, but these errors were encountered:
Hm, I can't reproduce the wrong language tooltip issue...
This value seems to be set by the browser itself, for the datetime-local input field type. At least the error message in red that we display is in the correct language :)
Played around with the lock time in the wallet and found these bugs.
If I type the locktime without mouseclicks i get 6 numbers in the year. example: 19.05.202344 --:--
When I use the arrow keys on the keyboard to go back or forward by 1 year, the number 275760 appears as the year before 2023, maybe it could be stopped by 2023 or the actual year.
After setting the lock time, for example: 20.05.2024 10:00, if I want to correct the year afterwards, it jumps to 1901, and I can only change the last digit, from 1901 to 1909.
When I hover over the field, strangely I get a pop-up in German even though the wallet is set to English. Gib einen gültigen Wert ein, das Feld ist nicht vollständig...
The text was updated successfully, but these errors were encountered: