GitLab

Before this change, an empty value was causing a failure state
only if no other values existed. The empty value was skipped for
filling and later on (maybe) failed in the empty-check. If the
field was filled by outside forces (e.g. cached by website)
the skipped value would not cause a failure state.

This behaviour was causing inconsistent results.

After this change, an empty value will always cause a failure
state immediately and not attempt the filling.

Bug: b/175270472
Change-Id: I939e2069e237d960ebf3a826a799e5ab23ecc4c9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2582323Reviewed-by: Mathias Carlen <mcarlen@chromium.org>
Reviewed-by: Marian Fechete <marianfe@google.com>
Commit-Queue: Sandro Maggi <sandromaggi@google.com>
Cr-Commit-Position: refs/heads/master@{#836061}