New issue
Advanced search Search tips

Issue 691021 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android
Pri: 3
Type: Bug

Blocking:
issue 770175



Sign in to add a comment

Washington Post website does not fill in username/password of user

Project Member Reported by rouslan@chromium.org, Feb 10 2017

Issue description

What steps will reproduce the problem?
(1) Subscribe to https://www.washingtonpost.com in Chrome on Android.
(2) Open https://www.washingtonpost.com in Chrome on Linux.

What is the expected result?
Chrome on Linux should prefill username/password fields.

What happens instead?
Chrome on Linux did not prefill username/password fields.

 

Comment 1 by rogerm@chromium.org, Feb 24 2017

Owner: vabr@chromium.org
Does chrome on android still not fill for you?

Maybe diff between subdomains for mobile and desktop sites?

You're syncing passwords?


Chrome on Android currently fills my email into the username field, but does not fill the password field.

Domain is https://subscribe.washingtonpost.com in both cases.

Passwords are syncing, but chrome://settings/passwords does not show a password for Washginton Post. I'm guessing the password manager did not recognize the account signup form.

Comment 3 by rogerm@chromium.org, Feb 24 2017

vabr, the first field is classified as email. could the password filling be supressed because it's seeing email + password instead of username + password?

Comment 4 by vabr@chromium.org, Feb 27 2017

Cc: kolos@chromium.org
Components: -UI>Browser>Autofill UI>Browser>Passwords
Labels: Hotlist-Polish
Owner: ----
Status: Available (was: Untriaged)
Thanks for the analysis!
I think kolos@ could know the answer to #3.

Meanwhile, moving this to the passwords component and marking as available in our queue.

Comment 5 by kolos@chromium.org, Apr 11 2017

I tested it, but I created an account instead of subscribing in step 1) Saving and autofilling works for me in M57.

Comment 6 by kolos@chromium.org, Jan 26 2018

Blocking: 770175

Comment 7 by kolos@chromium.org, Jan 26 2018

Status: Fixed (was: Available)
Based on #5, it is Fixed. Perhaps there was a problem with sync. 

Sign in to add a comment