Name | Date | Size | #Lines | LOC | ||
---|---|---|---|---|---|---|
.. | 03-May-2022 | - | ||||
android/ | H | 16-Feb-2021 | - | 4,501 | 3,321 | |
content/ | H | 16-Feb-2021 | - | 16,513 | 11,738 | |
core/ | H | 16-Feb-2021 | - | 193,838 | 139,959 | |
ios/ | H | 16-Feb-2021 | - | 6,003 | 4,661 | |
DEPS | H A D | 16-Feb-2021 | 561 | 20 | 17 | |
OWNERS | H A D | 16-Feb-2021 | 315 | 16 | 14 | |
PRESUBMIT.py | H A D | 16-Feb-2021 | 2.9 KiB | 78 | 62 | |
README | H A D | 16-Feb-2021 | 1.2 KiB | 24 | 18 |
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