[Autofill] Merge content_autofill_features.{h,cc} with autofill_features.{h,cc}
The argument for introducing content_autofill_features.{h,cc} was
a "conceptual layering violation" [1]. That's a fair point, but the
same argument applies to many other existing features (e.g., some
payments features). Autofill's current practice is apparently to
to organize the features more by team than by architecture.
Therefore, this CL moves `kAutofillSharedStorageServerCardData` to
autofill_payments_features.{cc,h}.
[1] https://chromium-review.googlesource.com/c/chromium/src/+/5199136/comment/e12b2128_05fb46c4/
Bug: 40100455
Change-Id: If938161b1e66074f4585cf6a8dbb9253a1069a41
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6039765
Commit-Queue: Christoph Schwering <schwering@google.com>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1386838}
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.