Pull FindUsernameInPredictions out of html_based_username_detector.cc
The HTML based username detector first computes an ordered list of potential usernames out of all form fields, and then tries to identify the front-most of that list which is also on a list of plausible username fields computed by other parts of Chrome. This bundling may become a source of trouble once most of the parsing code, including the one which produces the plausible username fields, gets moved to a different process (renderer -> browser) and will get run after the HTML classifier. To solve this problem, this CL keeps the first part within html_based_username_detector.cc, but moves the latter to the callsite, the password_form_conversion_utils.cc. This way the HTML based detector only needs the list of all form fields and loses its dependency on the code computing the plausible fields. Bug: 833838 Change-Id: I66eef8098cd523c52fc54d02197a46382ada2fc6 Reviewed-on: https://chromium-review.googlesource.com/1032738Reviewed-by:Vadym Doroshenko <dvadym@chromium.org> Commit-Queue: Vaclav Brozek <vabr@chromium.org> Cr-Commit-Position: refs/heads/master@{#559093}
Showing
Please register or sign in to comment