Chrome autofill fails after N times
Reported by
roman....@inveritasoft.com,
Sep 11
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Example URL: http://46.101.229.197:4444/account/login Steps to reproduce the problem: 1. Save email and password in the Chrome credentials registry 2. Reload the page 3. See autofilled login form 4. Go to the register form 5. Go to the login form 7. Repeat register to login 5 more times 8. See that login form was not autofilled, though previous attempts were correct DON'T RELOAD THE PAGE! What is the expected behavior? Step 8. all attempts should be autofilled What went wrong? The form was not autofilled after N atteempts Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? No Does this work in other browsers? Yes Chrome version: 68.0.3440.106 Channel: n/a OS Version: OS X 10.13.6 Flash Version: For SPA stuff things should be stable.
,
Sep 12
Instruction are not clear but the gif seems to show that the repro case is to click login and forgot password entries to see that things are not working after a while. Is that correct? I tried that many times, and each time the login page was filled in.
,
Sep 12
Tested and it is reproducible on other machines (Windows 10 and MacOs High Siera). It does stops working after 6 attempts. Also the login form should be filled automatically! For reproduce only the login/register button should be clicked, and dropdown for inputs shouldn't be in use
,
Sep 12
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 12
,
Sep 12
,
Sep 14
,
Sep 14
We implemented this as a stop gap in case the password manager has problems filling forms and runs into an infinite loop, draining your battery and blocking the CPU. I think it is rare enough that people switch between sign-up and sign-in forms 6 times that we can accept that the behavior is not perfect here.
,
Sep 14
Reasoning is good, but I don't agree with you. If feature exists, would be nice to have this in stable state. Otherwise lets agree that Chrome Autofill is unstable (infinite loop, battery drain, CPU block, limited attempts).
,
Sep 14
For now using experimental feature navigation.credentials API to fix this browser behaviour, but its experimental, so not stable as well. Our specifications are somehow relying on this "edge case" that has some UI/UX workaround. But still users are relying on this stuff. With regards |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by roman....@inveritasoft.com
, Sep 11