Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PIN entered not shown until window moves #453

Closed
Ottunger opened this issue Nov 8, 2021 · 7 comments
Closed

PIN entered not shown until window moves #453

Ottunger opened this issue Nov 8, 2021 · 7 comments
Assignees
Labels

Comments

@Ottunger
Copy link
Contributor

Ottunger commented Nov 8, 2021

Maybe hard to see on attached video: while entering card PIN, the input does not show "dots" for each number types, only after window is moved do we see the dots. This may be confusing for user who may think nothing is being entered.

screen-capture.mp4
@donskov
Copy link
Collaborator

donskov commented Nov 8, 2021

@Ottunger Thanks for the report. You are right and we managed to reproduce it on our own.

We will try to fix it as soon as possible.

@donskov
Copy link
Collaborator

donskov commented Nov 8, 2021

@Ottunger Could you share your machine information (memory, CPU, etc.)?

We reproduced this bug only on machines with low resources. When we increase resources - the bug disappears.

@Ottunger
Copy link
Contributor Author

Ottunger commented Nov 8, 2021

Win 10 x64

image

@Ottunger
Copy link
Contributor Author

Ottunger commented Nov 9, 2021

Sometimes I see it too myself, usually when I just started Fortify.
The application does not seem to leak too much memory though.

I cannot investigate more than this unfortunately.

@donskov donskov added the bug label Nov 9, 2021
@donskov
Copy link
Collaborator

donskov commented Nov 10, 2021

@Ottunger Please try to use the updated version.

@donskov donskov self-assigned this Nov 11, 2021
@Ottunger
Copy link
Contributor Author

Hi @donskov , I confirm it seems fixed to me :)

@donskov
Copy link
Collaborator

donskov commented Nov 12, 2021

Thanks, @Ottunger. I will update the 1.8.3 release with this fix.

@donskov donskov mentioned this issue Nov 12, 2021
@donskov donskov closed this as completed Nov 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants