Teach form parser consider interactability
The FormData -> PasswordForm password needs to distinguish three levels of interactability of fields: fields already interacted with, fields likely to be interacted with, and those which are unlikely. This is what the old parser in password_form_conversion_utils.cc called filtering levels. The interactability is useful when identifying whether an obtained result is potentially useful. Also, the structural analysis only should consider the fields with best interactability. This CL introduces the concept of interactability and restricts the structural analysis ("base heuristics") to fields with best interactability. The CL does not introduce interactability-based penalties yet, because the confidence rating is not implemented yet. (See details in the design doc linked from the bug description.) Bug: 845426 Change-Id: Ib0dd2f9837c537e4d64432a35b7ba2f5f8e72403 Reviewed-on: https://chromium-review.googlesource.com/1099060Reviewed-by:Vadym Doroshenko <dvadym@chromium.org> Commit-Queue: Vaclav Brozek <vabr@chromium.org> Cr-Commit-Position: refs/heads/master@{#567232}
Showing
Please register or sign in to comment