sap.m.Input: changing type from Password to Text stops updating JSONModel value binding

[user1545]

What is the issue and how can we reproduce it?

When a sap.m.Input is bound to a JSON model via its value property, the binding appears to stop updating the model after the input type is switched from Password to Text.

Reproduction steps

1. Open the sample:
   https://jsbin.com/hijerepuhe/edit?html,output

2. Enter a value into the input while it is still in Password mode.

3. Click Show Password
   -> The entered value is shown correctly.

4. Reload the sample.

5. Enter a value into the input while it is in Password mode.

6. Click the value help icon (show) so that the input type changes from Password to Text.

7. Click Show Password

What is the expected result?

The value entered in the input should still be available in the bound JSON model after switching the input type from Password to Text.

oModel.getProperty("/inputValue") should return the current value in both cases.

What happens instead?

After switching the input type from Password to Text, the model no longer seems to receive the current value.

As a result, clicking the button shows an empty or missing password value although text is visible in the input field.

Which OpenUI5 version is your project targeting?

1.146.0

Is the issue device- or browser-specific?

Not browser-specific, tested:
Chrome, Firefox

Confirmation

• I have searched the existing issues and reviewed the relevant documentation as well as the API reference.
• I am not disclosing any internal or sensitive information.

[didip1000]

Hello @user1545,

Thank you for your report, the issue is internally tracked as DINC0859460. Any updates will be communicated here.

Best,
Diana

[nikoletavnv]

Hello @user1545,

I am analyzing the issue you have reported but I am not able to open the sample from the link you have provided because of invalid SSL certificate. Can you please provide us with other sample so we can continue identify the issue.

Kind regards,
Nikoleta

[user1545]

Hi Nikoleta,

I’ve put the example into JSFiddle for you.

https://jsfiddle.net/kmyc6fha/

Best Regards,
user1545

[nikoletavnv]

Hi @user1545,
Thank you for the sample.

The valueHelp functionality is used for helping selecting input values and has some restrictions in your use case. The underlying model is not updated immediately after you press the value help icon to switch between input modes. The idea of the value help icon is to be part of the input and pressing it does not trigger change event because you are inside the input field. We are specifically listening for value help icon press and do not fire a change of the value, that would also update the model.
Another approach you can take is to use the input addEndIcon method to add "show/hide" icon in the input in order to change the input type from password to text and vice versa.
Here is an example how to do it:

const oInput = new Input({
						value: "{/inputValue}",
						type: "Password",
						placeholder: "Enter password",
					});

					const oIcon = oInput.addEndIcon({
						src: "sap-icon://show",
						press: function (){
							if (this.getType() === "Password") {
								this.setType("Text");
								oIcon.setSrc("sap-icon://hide");
							} else {
								this.setType("Password");
								oIcon.setSrc("sap-icon://show");
							}
						}.bind(oInput)
					});

Please let us know if this change fulfils your scenario.

Kind regards,
Nikoleta

[user1545]

Hi Nikoleta,

thanks, that works for me.

That said, showing/hiding passwords via valueHelp is actually quite a common pattern if you look it up. For example:
#3363
https://community.sap.com/t5/technology-q-a/show-hide-password-in-sapui5/qaq-p/11551810

So I’m wondering how many people might not even realize that a workaround is needed in the first place.

The tricky part is that this issue is extremely hard to detect because it occurs so rarely. At first, you tend to assume that end users are simply entering their passwords incorrectly—especially since it eventually works.

Once you realize that it’s unlikely to be caused by user errors, your suspicion shifts toward the hashing or encryption logic behind the password—particularly since the issue is not consistently reproducible.
However, debugging those parts in a productive environment is practically impossible.

So I think it would take quite a long time to figure this out, and I’m afraid many people using show/hide via valueHelp are not aware of this yet.

In any case, this won’t affect me again, so you can go ahead and close the issue.
Thank you very much.

Best regards,
user1545