Password visibility toggle inverted ?

[Bertrand]

Hi,

I'm testing SfTextInputLayout and the EnablePasswordVisibilityToggle option.

Something is bothering me : the password is visible when the strikethrough eye icon is displayed

I think it should be the contrary. Or maybe I'm misunderstanding something... ?

Thanks

Bertrand

Version 16.3.0.21

[Michael Prabhu M]

Hi Bertrand,  

  

Greetings from Syncfusion,   

  

EnablePasswordVisibilityToggle of SfTextInputLayout control is used to display / collapse the toggle button. Whereas the password visibility functionality of this toggle button depends on the `IsPassword` property of Entry. It is false by default.  

 

Please look into the below link for better understanding.  

 

https://docs.microsoft.com/en-us/dotnet/api/xamarin.forms.entry.ispassword?view=xamarin-forms#Xamarin_Forms_Entry_IsPassword   

 

https://help.syncfusion.com/xamarin/sftextinputlayout/getting-started#enabling-password-visibility-toggle      

 

Hope this helps.  

 

Thanks, 

Michael 

 

[Bertrand]

Maybe there is a misunderstanding...

I'm refering to this page : https://help.syncfusion.com/xamarin/sftextinputlayout/getting-started#enabling-password-visibility-toggle

Of course I'm assuming IsPassword=true on the Entry.

It still seems to me that the password should be visible when the eye icon is displayed, not the contrary.

[Michael Prabhu M]

Hi Bertrand, 

 

Sorry for the confusion from our user guide document, but as explained in the previous update, the EnablePasswordVisibilityToggle is used to enable or disable the button (eye button) alone. If you have used an Entry inside the SfTextInputLayout you have to use the Entry’s property “IsPassword” to enable the visibility of characters in the Entry.  

 

We will change the User Guide document to clearly depict the above in few days. Thanks for your feedback. 

 

Thanks, 

Michael 

[Bertrand]

I'm very sorry for the misunderstanding, but the usage of IsPassword and EnablePasswordVisibilityToggle is already perfectly explained in the user guide, and I'm not questionning it.

So let me reformulate my question once again :

Why is the striked eye icon displayed when the password is visible, and the open eye icon displayed when the password is hidden ?

I believe it should be the contrary.

[Michael Prabhu M]

Hi Bertrand, 

 

Sorry for the misunderstanding from my side, the below image explains it clearly, 

 

For representation purpose, we have changed the icon with the text. 

 

 

 

 

So, the Open eye icon denotes “Show password” and the Strike eye icon denotes the “Hide password” functionality. Even when you log into any windows 10 machine you can see the open eye icon will be displayed when you type in a password and the open eye will be clicked and hold to view the password, similar we have kept the open eye to show and we have added the strike eye to hide and this is the behavior of our control. 

 

Thanks, 

Michael  

 

[Bertrand]

Well, while I appreciate your efforts for clarifying how this functionality has been designed, I still disagree :)

Please take a look at this video showing what I assume is the standard behavior and implementation for the eye icon: 

https://www.youtube.com/watch?v=dW0YIV0Z9qk

What do you think ?

[Michael Prabhu M]

Hi Bertrand, 

Thanks for the update, the behavior we have provided for password toggle icon is also correct and the same behavior is used in flutter and some other applications. However, we will analysis further on this to know which one of the behaviors is most preferred and understandable by the users and will reverse the behavior if necessary. As of now, you can achieve the required behavior by hiding the password visibility toggle icon and configuring the trailing view. If you need an example, please let us know we will provide you a simple example with trailing view to achieve the requested behavior. 

Thanks, 

Michael 

[Bertrand]

Hi,

It looks like the behavior has been modified recently.

Could you please post in this thread the corresponding release number ?

Thanks

Bertrand

[Bharathiraja K]

Hi Bertrand,

Yes, we have changed the behavior in last release 16.4.0.42 version according the Google login behavior.

Regards, 

Bharathiraja.