Rebecca Chang Swee Fun 9cc2b9099d components: autofill: set -fbracket-depth=1000 1 year ago
..
android 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
content 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
core 9cc2b9099d components: autofill: set -fbracket-depth=1000 1 year ago
ios 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
COMMON_METADATA 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
DEPS 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
DIR_METADATA 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
OWNERS 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
PRESUBMIT.py 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
README 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago

README

Autofill is in the process of becoming a layered component
(https://sites.google.com/a/chromium.org/dev/developers/design-documents/layered-components-design)
to enable it to be shared cleanly on iOS.

When this process is complete, this component will have the following structure:

- core/: shared code that does not depend on src/content/ or src/ios/
- browser/: Browser process code
- common/: Code shared by the browser and the renderer
- content/: Driver for the shared code based on the content layer.
- browser/: Browser process code.
- renderer/: Renderer process code.
- common/: Code shared by the browser and the renderer.
- ios/: Driver for the shared code based on src/ios.

See
https://sites.google.com/a/chromium.org/dev/developers/design-documents/layered-components-technical-approach/making-autofill-into-a-layered-component
for an outline of the project.

For pointers on how to continue getting your work done as the component moves
into its new structure, see
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-