Don't delay password requirements fetching after autofill responds
Chrome used to fetch password requirements specifications once the Autofill server responded. This means that two network round trips were necessary until the data was available. With this change, the requirements are fetched every time the renderer reports that password forms were found, which moves the lookup to an earlier point. As this reporting can happen multiple times through the life-cycle of a site, the CL also introduces an extra in-memory cache lookup that prevents further processing if the requirements have been fetched already. Bug: 873653, 846694 Change-Id: Id1bdd575fa659fcf05b40a937cb6aa00206e8965 Reviewed-on: https://chromium-review.googlesource.com/1172972Reviewed-by:Vadym Doroshenko <dvadym@chromium.org> Commit-Queue: Dominic Battré <battre@chromium.org> Cr-Commit-Position: refs/heads/master@{#582912}
Showing
Please register or sign in to comment