
Use a feature flag instead of an indirect strategy to enable the feature to set the is_user_edited bit in parsed fields. As is_user_edited has been no op for a while (probably since Jun 2023 where we did the JS -> TS migration, http://crrev.com/c/https://chromium-review.googlesource.com/c/chromium/src/+/4611286), we should do a feature gated rollout so we can measure the impact of fixing is_user_edited. With the fix, is_user_edited is set to false by default then flipped to true as soon as a user "input" is detected in the field, whereas right now is_user_edited is always set to true. With the fix we expect more perfect fills (metric-wise not in reality) and maybe a bit more card updates. R=tmartino@chromium.org Change-Id: I1b0227740213297e4fda5c8db02661cdcaa41466 Fixed: 397440877 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6281435 Reviewed-by: Tommy Martino <tmartino@chromium.org> Commit-Queue: Vincent Boisselle <vincb@google.com> Cr-Commit-Position: refs/heads/main@{#1423460}
This directory holds code related to Chrome for iOS. See this document for a description of the structure underneath this directory.