username and password are not autofilled on cvs.com |
|||||||||
Issue descriptionApp Version:59.0.3054.0 iOS Version: iOs10.3.1 Device: iPhone7 URL: cvs.com Steps to reproduce: 1. On desktop (signed in for sync) go to cvs.com and login, opt to save the u/p 2. On ios, open Chrome (signed in for sync), go to cvs.com 3. Tap menu->sign in Observed results: username and password are not autofilled or offered from the keyboard toolbar. Expected results: Username and password are never filled in. Note: both are filled in on desktop. Number of times you were able to reproduce: 5/5 Bug reproducible after clean install:Yes Bug reproducible after clearing cache and cookies:Yes Observed behavior in Chrome Mobile on Android: n/a Check for similar behavior on Firefox/Safari: n/a Bug reproducible on current stable build (App Version, iOS Version): Yes M57 Bug reproducible on the current beta channel build (App Version, iOS Version): Yes M58
,
Apr 6 2017
,
Apr 7 2017
,
Apr 13 2017
,
Apr 13 2017
I cannot access the cvs.com site from Germany. To help us predict whether a planned refactoring might fix this, could someone confirm whether the desktop version works fine?
,
Apr 13 2017
,
Apr 13 2017
Hi, In comment 0 there is "Note: both are filled in on desktop." I'll remove the roadblock label.
,
Apr 14 2017
Thanks! I missed that. The new label I'm adding expresses: This is working on desktop and hence likely to be fixed once we start sharing desktop heuristics with iOS code.
,
Apr 24 2017
cvs.com actually works, but there is a catch which makes it confusing: Just typing "cvs.com" on desktop or iPad results in http://cvs.com. Doing the same on iPhone leads to https://m.cvs.com. Notice that the scheme is different: HTTP in the first case, HTTPS on iPhone. Since 58, Chrome (including on iOS) will allow to migrate credentials stored on a HTTP site to the HTTPS version of the same site. Currently, however, this only works with the same domain. In this case, the domain also changed (cvs.com -> m.cvs.com). That will be supported, but is work in progress. Once the HTTPS credentials are saved, though, the mobile page is filled with no problem on iPhone as well. Hence closing this. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by liaoyuke@chromium.org
, Apr 6 2017Owner: vabr@chromium.org
Status: Assigned (was: Untriaged)