bisq
bisq copied to clipboard
Wallet Date input field marches across the screen
Description
The width of date input fields for Wallet Date keeps increasing. The calendar icon marches across the app and off the edge.
Version
v1.9.1
Steps to reproduce
Go to Account > Wallet Seed
Expected behaviour
Width of wallet date inputs should be constant
Actual behaviour
The Date Input fields keep increasing in width until the it takes up over 100% of the width of the app itself.
Screenshots
When I first go to the Wallet Seed screen:
Several seconds later:
It doesn't stop:
Device or machine
MacOS 12.3.1
Thanks for opening your first issue here!
Be sure to follow the issue template. Your issue will be reviewed by a maintainer and labeled for further action.
Has this been fixed or is it still an issue? Does not occur on my side in Windows.
Reproduced today on a first time install of version 1.9.5 on MacOS 12.5.1 (21G83).
The impact of this bug is that those fields become unusable.
This problem persists for the lifetime of the app, so the workaround is to close the app and reopen it and be quick.
I can't reproduce this.. maybe it's a MacOS only issue.
There's also another date picker in the following view: open Bisq > click on FORGOT PASSWORD? button. Does it also occur in that window?
@Android-X13 seems you identified a fix for this issue, will you be making a PR to address the problem in Bisq?
@jmacxx Unfortunately I don't have a Mac and I can't reproduce the issue. I could submit a PR but it would be a blind fix... I won't be able to test it.
@Android-X13 Please submit the fix, there are Mac users | devs who can validate it.
Reproduced today on 1.9.9/MacOS.
This is a massive glaring problem and faces the user the first time they open the account page (for me my app opened at this page).
Extremely confusing and worrying for new users, that their new app in an ecosystem that they want to try to trust is acting screwy from the get-go.
It would be helpful if someone with a Mac can try out the fix #6602.
Is there an easy way for me to grab a build of this? I'm happy to see if that change fixes it.
Still a bug on Mac M1/ 1.9.14