webapp: Google Chrome asks to "update password" without any reason #2741
Assignees
Milestone
Comments
|
Does your project use the cn1-native-controls library at all? If you can't produce a test case, can you provide the HTML content of the DOM when this occurs? You can copy the DOM as text in the Chrome inspector using the Copy OuterHTML option.
|
|
Thank you for the tip about copying html content. Screenshot: Code: |
|
Is there a password field anywhere in the app, e.g. in the previous form before this one? |
|
Yes, as I previously wrote:
|
|
I haven't been able to reproduce this, but I've made a small change that might fix it. This will be included in the next update. |
|
Thank you, I'll wait for it. |
|
And... why does Google Chrome store the password without the username? |
|
It is because we reuse a single native The cn1-native-controls addresses this issue by wrapping a separate native text field for each NTextField widget so that password managers can find both the username and password fields. There are negative aspects of the "one native field per lightweight field" strategy, so the only use case I recommend for NTextField is for usernames and passwords (login forms). |
|
So the cn1-native-controls could be the solution for the issue that I reported, because the text field used for the password is not the same used for other fields, right? |
|
Your fix didn't solve this issue. Of course this is not the solution, but a temporary acceptable fix that avoid a lot of problems. Now I have a code like: |
shannah
added a commit
that referenced
this issue
Mar 26, 2019
|
I added the test case that I was using to try to reproduce this issue. So far I can't reproduce it. If you can modify this test case to reproduce the issue, I can take another look. |
|
Can't reproduce. Closing. Will reproduce if a test case is provided. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unfortunately I cannot create a test case: I've done a lot of trials to produce a test case, without success.
However, I try to describe my issue.
I have a
Forminside aForm. The innerFormhas a toolbar and aTextModeLayout, which contains fourInputComponents: oneTextComponent(with constraintTextArea.INITIAL_CAPS_WORD, twoPickerComponentsand oneAutoCompleteTextComponentfor the search of a city (an example code ofAutoCompleteTextComponentis here: #2705).The issue is that Google Chrome shows a box that asks to update the password when the user change the text in the two
TextComponent.There is no
InputComponentin that form that hasTextArea.PASSWORDas constraint, so this request has no sense. This problem is absent in Safari or in native apps.The password manager of Google Chrome reports the wrong updated password (that is the text entered in the first
TextComponent), with an empty user name.The web-app has also a login form with two
InputComponents, the first one is aTextComponentwith the constraintTextArea.USERNAME, the second one is aTextComponentPassword(similar to: #2654): I noted that Google Chrome stores in the password manager only the password without the username. However, if I replace theTextComponentPasswordwith aTextComponentthat has constraintTextArea.PASSWORD, nothing changes: the issue is the same (password stored without username and request to update the password when there is no password in theForm).I don't know how to solve this issue. Any help or idea?
The text was updated successfully, but these errors were encountered: