Name | Date | Size | #Lines | LOC | ||
---|---|---|---|---|---|---|
.. | 03-May-2022 | - | ||||
android/ | H | 12-Nov-2020 | - | 3,808 | 2,861 | |
content/ | H | 12-Nov-2020 | - | 16,050 | 11,419 | |
core/ | H | 12-Nov-2020 | - | 165,699 | 118,829 | |
ios/ | H | 12-Nov-2020 | - | 5,195 | 4,041 | |
DEPS | H A D | 07-Nov-2020 | 561 | 20 | 17 | |
OWNERS | H A D | 07-Nov-2020 | 240 | 13 | 11 | |
PRESUBMIT.py | H A D | 07-Nov-2020 | 1.9 KiB | 53 | 40 | |
README | H A D | 07-Nov-2020 | 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