commit | f00c2f7f43bac2779b769ff7967d848c78c15a65 | [log] [tgz] |
---|---|---|
author | Christoph Schwering <schwering@google.com> | Sat Jul 26 04:11:40 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Jul 26 04:11:40 2025 |
tree | 032d3c8ce7622d5bbc4b1cf93dcd6fba00b462b1 | |
parent | 4682e864617746dc6ee183fe6a96de0a1082817b [diff] |
[Autofill] Do not merge UNKNOWN_TYPE and HtmlFieldType::kUnrecognized After this CL, AutofillType(HtmlFieldType::kUnrecognized).ToStringView() no longer returns "UNKNOWN_TYPE" but "HTML_TYPE_UNRECOGNIZED". That change affects the following callers: - Some logging functions: They which benefit from distinguishing between UNKNOWN_TYPE and HtmlFieldType::kUnrecognized. - autofill_feedback_data.cc: Same as logging. - automation_app_interface.mm: Its doing reverse lookup that currently maps "UNKNOWN_TYPE" to HtmlFieldTypeToBestCorrespondingFieldType(kUnrecognized). That happens to work fine because the function returns UNKNOWN_TYPE. But this CL makes the reverse lookup more reliable. - WebView: This change provides more information to the Autofill framework by distinguishing between UNKNOWN_TYPE and HtmlFieldType::kUnrecognized. This change is admissible because Autofill doesn't guarantee these strings to be stable. Bug: 40100455 Change-Id: Ic61722c1e9228f8efa81f8e91f15f3cd788b3e6b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6786127 Commit-Queue: Christoph Schwering <schwering@google.com> Reviewed-by: Dominic Battré <battre@chromium.org> Cr-Commit-Position: refs/heads/main@{#1492395}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.