Commit 3714ff73 authored by Vadym Doroshenko's avatar Vadym Doroshenko Committed by Commit Bot

Make new form parser features consistent.

The new form parsing for saving requires the new parsing for filling is
available. This CL enforces it.

Bug: 831123
Change-Id: I9b2463f5e80ef51a267325dfdb3b576f244d15e5
Reviewed-on: https://chromium-review.googlesource.com/c/1282952Reviewed-by: default avatarVadym Doroshenko <dvadym@chromium.org>
Reviewed-by: default avatarVaclav Brozek <vabr@chromium.org>
Commit-Queue: Vadym Doroshenko <dvadym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#600017}
parent 804659ab
...@@ -406,8 +406,10 @@ void PasswordManager::RegisterLocalPrefs(PrefRegistrySimple* registry) { ...@@ -406,8 +406,10 @@ void PasswordManager::RegisterLocalPrefs(PrefRegistrySimple* registry) {
PasswordManager::PasswordManager(PasswordManagerClient* client) PasswordManager::PasswordManager(PasswordManagerClient* client)
: client_(client), : client_(client),
is_new_form_parsing_for_saving_enabled_(base::FeatureList::IsEnabled( is_new_form_parsing_for_saving_enabled_(
features::kNewPasswordFormParsingForSaving)) { base::FeatureList::IsEnabled(
features::kNewPasswordFormParsingForSaving) &&
base::FeatureList::IsEnabled(features::kNewPasswordFormParsing)) {
DCHECK(client_); DCHECK(client_);
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment