• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

android/H12-Nov-2020-3,8082,861

content/H12-Nov-2020-16,05011,419

core/H12-Nov-2020-165,699118,829

ios/H12-Nov-2020-5,1954,041

DEPSH A D07-Nov-2020561 2017

OWNERSH A D07-Nov-2020240 1311

PRESUBMIT.pyH A D07-Nov-20201.9 KiB5340

READMEH A D07-Nov-20201.2 KiB2418

README

1Autofill is in the process of becoming a layered component
2(https://sites.google.com/a/chromium.org/dev/developers/design-documents/layered-components-design)
3to enable it to be shared cleanly on iOS.
4
5When this process is complete, this component will have the following structure:
6
7- core/: shared code that does not depend on src/content/ or src/ios/
8  - browser/: Browser process code
9  - common/: Code shared by the browser and the renderer
10- content/: Driver for the shared code based on the content layer.
11  - browser/: Browser process code.
12  - renderer/: Renderer process code.
13  - common/: Code shared by the browser and the renderer.
14- ios/: Driver for the shared code based on src/ios.
15
16See
17https://sites.google.com/a/chromium.org/dev/developers/design-documents/layered-components-technical-approach/making-autofill-into-a-layered-component
18for an outline of the project.
19
20For pointers on how to continue getting your work done as the component moves
21into its new structure, see
22https://sites.google.com/a/chromium.org/dev/developers/design-documents/layered-components-technical-approach/making-autofill-into-a-layered-component#TOC-Help-How-Do-I-Get-My-Autofill-Related-Work-Done-
23
24