components/android_autofill/browser/android_autofill_features.cc

// Copyright 2023 The Chromium Authors
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

#include "components/android_autofill/browser/android_autofill_features.h"

#include <jni.h>

#include "base/feature_list.h"
#include "components/android_autofill/browser/jni_headers_features/AndroidAutofillFeatures_jni.h"

namespace autofill::features {

namespace {

const base::Feature* kFeaturesExposedToJava[] = {
    &kAndroidAutofillBottomSheetWorkaround,
    &kAndroidAutofillPrefillRequestsForLoginForms,
    &kAndroidAutofillSupportVisibilityChanges,
    &kAndroidAutofillUsePwmPredictionsForOverrides,
};

}  // namespace

// If enabled, we send SparseArrayWithWorkaround class as the PrefillHints for
// the platform API `AutofillManager.notifyViewReady()` as a workaround for the
// platform bug, see the comment on the class. This works as a kill switch for
// the workaround in case any unexpected thing goes wrong.
BASE_FEATURE(kAndroidAutofillBottomSheetWorkaround,
             "AndroidAutofillBottomSheetWorkaround",
             base::FEATURE_ENABLED_BY_DEFAULT);

// If enabled, we explicitly cancel the ongoing Android autofill session on new
// document navigation by calling `AutofillManager.cancel()`, we clear the
// request state in the java side as it works as an indicator to the current
// session.
BASE_FEATURE(kAndroidAutofillCancelSessionOnNavigation,
             "AndroidAutofillCancelSessionOnNavigation",
             base::FEATURE_DISABLED_BY_DEFAULT);

// If enabled, prefill requests (i.e. calls to
// `AutofillManager.notifyVirtualViewsReady`) are supported. Such prefill
// requests are sent at most once per WebView session and are limited to forms
// that are assumed to be login forms.
// Future features may extend prefill requests to more form types.
BASE_FEATURE(kAndroidAutofillPrefillRequestsForLoginForms,
             "AndroidAutofillPrefillRequestsForLoginForms",
             base::FEATURE_DISABLED_BY_DEFAULT);

// If enabled, visibility changes of form fields of the form of an ongoing
// Autofill session are communicated to Android's `AutofillManager` by calling
// `AutofillManager.notifyViewVisibilityChanged()`.
// See
// https://developer.android.com/reference/android/view/autofill/AutofillManager#notifyViewVisibilityChanged(android.view.View,%20int,%20boolean)
// for more details on the API.
BASE_FEATURE(kAndroidAutofillSupportVisibilityChanges,
             "AndroidAutofillSupportVisibilityChanges",
             base::FEATURE_ENABLED_BY_DEFAULT);

// If enabled, username and password field predictions are taken from
// `password_manager::FormDataParser` and overwrite Autofill's native
// predictions. Furthermore, similarity checks between cached forms and focused
// forms that serve to decide whether to show a bottomsheet are performed using
// these predictions: Two forms are considered similar iff they have the same
// `FormDataParser` predictions.
BASE_FEATURE(kAndroidAutofillUsePwmPredictionsForOverrides,
             "AndroidAutofillUsePwmPredictionsForOverrides",
             base::FEATURE_DISABLED_BY_DEFAULT);

// If enabled, offer prefill requests (i.e. calls to
// `AutofillManager.notifyVirtualViewsReady`) to change
// password forms as well. A form can't be login and change password at the same
// time so order of the check whether it's login or change password shouldn't
// matter.
BASE_FEATURE(kAndroidAutofillPrefillRequestsForChangePassword,
             "AndroidAutofillPrefillRequestsForChangePassword",
             base::FEATURE_DISABLED_BY_DEFAULT);

static jlong JNI_AndroidAutofillFeatures_GetFeature(JNIEnv* env, jint ordinal) {
  return reinterpret_cast<jlong>(kFeaturesExposedToJava[ordinal]);
}

}  // namespace autofill::features