Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 Autofill is in the process of becoming a layered component | |
| 2 (https://sites.google.com/a/chromium.org/dev/developers/design-documents/layered -components-design) to enable it to be shared cleanly on iOS. | |
|
Jói
2013/06/05 19:08:55
Break after the closing parenthesis?
blundell
2013/06/06 07:23:48
Done.
| |
| 3 | |
| 4 When this process is complete, this component will have the following structure: | |
| 5 | |
| 6 - Top-level shared code that does not depend on src/content/ or src/ios/ | |
| 7 - content/: Driver for the shared code based on the content layer. | |
| 8 - browser/: Browser process code. | |
| 9 - renderer/: Renderer process code. | |
| 10 - common/: Code shared by the browser and the renderer. | |
| 11 - ios/: Driver for the shared code based on src/ios. | |
| 12 | |
| 13 See | |
| 14 https://sites.google.com/a/chromium.org/dev/developers/design-documents/layered- components-technical-approach/making-autofill-into-a-layered-component | |
| 15 for an outline of the project. | |
| 16 | |
| 17 For pointers on how to continue getting your work done as the component moves | |
| 18 into its new structure, see | |
| 19 https://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- | |
| 20 | |
| OLD | NEW |