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

Passwordbox issue #1139

Open
littlegend opened this issue Jun 20, 2024 · 8 comments
Open

Passwordbox issue #1139

littlegend opened this issue Jun 20, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@littlegend
Copy link

Describe the bug

when any char is used as the passwordchar and it happens to your password contains this char, unless this char is in the first poistion of your password, or the control would not accept your input to this char.

To Reproduce

  1. set passwordchar="*"
  2. input "abc*"
  3. you will find last char "*" can't be inputted
  4. set passwordchar="_"
  5. input "abc_"
  6. you will find last char "_" can't be inputted

Expected behavior

any legal char should be accepted no matter which char passwordchar is.

Screenshots

No response

OS version

Win11

.NET version

.NET 8 and .NET 4.8

WPF-UI NuGet version

3.0.4

Additional context

NA

@littlegend littlegend added the bug Something isn't working label Jun 20, 2024
@m0lDaViA
Copy link
Contributor

grafik
Don't know what you got, it's working for me.

@textGamex
Copy link
Contributor

textGamex commented Jun 21, 2024

grafik Don't know what you got, it's working for me.

I believe what he mean is to input at runtime, rather than assigning a value directly.

@m0lDaViA
Copy link
Contributor

grafik Don't know what you got, it's working for me.

I believe what he mean is to input at runtime, rather than assigning a value directly.

I did that too and it worked just fine for me.

@textGamex
Copy link
Contributor

grafik Don't know what you got, it's working for me.

I believe what he mean is to input at runtime, rather than assigning a value directly.

I did that too and it worked just fine for me.

That's peculiar, because in my development environment, I can consistently reproduce this bug.

@m0lDaViA
Copy link
Contributor

grafik Don't know what you got, it's working for me.

I believe what he mean is to input at runtime, rather than assigning a value directly.

I did that too and it worked just fine for me.

That's peculiar, because in my development environment, I can consistently reproduce this bug.

Can you take a video?

@textGamex
Copy link
Contributor

grafik Don't know what you got, it's working for me.

I believe what he mean is to input at runtime, rather than assigning a value directly.

I did that too and it worked just fine for me.

That's peculiar, because in my development environment, I can consistently reproduce this bug.

Can you take a video?

2024-06-21.23-46-44.mp4

@m0lDaViA
Copy link
Contributor

grafik Don't know what you got, it's working for me.

I believe what he mean is to input at runtime, rather than assigning a value directly.

I did that too and it worked just fine for me.

That's peculiar, because in my development environment, I can consistently reproduce this bug.

Can you take a video?

2024-06-21.23-46-44.mp4

Seems working to me.

@textGamex
Copy link
Contributor

grafik Don't know what you got, it's working for me.

I believe what he mean is to input at runtime, rather than assigning a value directly.

I did that too and it worked just fine for me.

That's peculiar, because in my development environment, I can consistently reproduce this bug.

Can you take a video?

2024-06-21.23-46-44.mp4

Seems working to me.

That is indeed peculiar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants