fix: disable Chrome address autofill prompts #140
+1
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
Summary
AutofillAddressEnabled: falseto the Chrome policy file to disable "save address" promptsAutofillCreditCardEnabled: falsewas already present for credit card promptsDetails
Policy names verified against Chromium source at:
/home/debianuser/chromium-cache/src/components/policy/resources/templates/policy_definitions/Miscellaneous/AutofillAddressEnabled.yaml/home/debianuser/chromium-cache/src/components/policy/resources/templates/policy_definitions/Miscellaneous/AutofillCreditCardEnabled.yamlThis follows the same approach used for KERNEL-432 (PasswordManagerEnabled) - adding entries to the managed policy JSON file that gets copied into the browser image.
Note
Low Risk
Single managed Chromium policy flag change that only affects browser autofill UX and does not touch auth, data storage, or backend logic.
Overview
Disables Chromium address autofill by adding
"AutofillAddressEnabled": falseto the managedpolicy.json, aligning it with existing disabled password and credit-card autofill settings to suppress “save address” prompts.Written by Cursor Bugbot for commit 2d00df3. This will update automatically on new commits. Configure here.